Skip to content

fix: upgrade tokio 0.2 to 1.x and futures 0.3.5 to 0.3.32 to resolve …#27

Closed
shivvinaykanswal wants to merge 2 commits intojayjun:masterfrom
invideoio:fix/upgrade-rust-deps-cves
Closed

fix: upgrade tokio 0.2 to 1.x and futures 0.3.5 to 0.3.32 to resolve …#27
shivvinaykanswal wants to merge 2 commits intojayjun:masterfrom
invideoio:fix/upgrade-rust-deps-cves

Conversation

@shivvinaykanswal
Copy link

…CVEs

Upgrades Rust dependencies to fix the following vulnerabilities:

Key changes:

  • tokio 0.2.13 -> 1.49.0 (basic_scheduler -> flavor="current_thread")
  • futures 0.3.5 -> 0.3.32
  • Replace tokio::prelude with explicit imports
  • Use AsyncRead::read instead of read_buf for stream processing
  • Use child.wait() instead of direct child future (tokio 1.x API)

shivvinay added 2 commits February 25, 2026 16:33
…CVEs

Upgrades Rust dependencies to fix the following vulnerabilities:
- CVE-2021-45710 / GHSA-rr8g-9fpq-6wmg / GHSA-4q83-7cq4-p6wg (tokio)
- CVE-2020-35906 (futures-task)
- CVE-2020-35905 (futures-util)
- CVE-2020-35711 (arc-swap, removed as transitive dep)
- CVE-2020-35919 / CVE-2020-35920 (net2/socket2, removed)
- CVE-2020-35921 (miow, removed)

Key changes:
- tokio 0.2.13 -> 1.49.0 (basic_scheduler -> flavor="current_thread")
- futures 0.3.5 -> 0.3.32
- Replace tokio::prelude with explicit imports
- Use AsyncRead::read instead of read_buf for stream processing
- Use child.wait() instead of direct child future (tokio 1.x API)
Pin tokio to =1.49.0 and futures to =0.3.32 instead of
relying on Cargo version resolution.
@invideoio invideoio closed this by deleting the head repository Feb 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants