Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RUSTSEC-2023-0018: sqlx-cli depends on vulnerable remove_dir_all version 0.7.0 #2755

Closed
aldur opened this issue Sep 15, 2023 · 2 comments · Fixed by #2757
Closed

RUSTSEC-2023-0018: sqlx-cli depends on vulnerable remove_dir_all version 0.7.0 #2755

aldur opened this issue Sep 15, 2023 · 2 comments · Fixed by #2757
Labels

Comments

@aldur
Copy link
Contributor

aldur commented Sep 15, 2023

Bug Description

RUSTSEC-2023-0018: sqlx-cli depends on vulnerable remove_dir_all version 0.7.0 (reference https://rustsec.org/advisories/RUSTSEC-2023-0018).

Minimal Reproduction

cargo audit
    Fetching advisory database from `https://github.com/RustSec/advisory-db.git`
      Loaded 570 security advisories (from /Users/aldur/.cargo/advisory-db)
    Updating crates.io index
    Scanning Cargo.lock for vulnerabilities (293 crate dependencies)
Crate:     remove_dir_all
Version:   0.7.0
Title:     Race Condition Enabling Link Following and Time-of-check Time-of-use (TOCTOU)
Date:      2023-02-24
ID:        RUSTSEC-2023-0018
URL:       https://rustsec.org/advisories/RUSTSEC-2023-0018
Solution:  Upgrade to >=0.8.0
Dependency tree:
remove_dir_all 0.7.0
└── sqlx-cli 0.7.1
    └── zap-it-later 0.1.0

error: 1 vulnerability found!

Info

  • SQLx version and features enabled: { version = "0.7.1", features = ["runtime-tokio", "sqlite", "chrono"] }
  • Database server and version: 3.39.5 2022-10-14 20:58:05 554764a6e721fab307c63a4f98cd958c8428a5d9d8edfde951858d6fd02daapl
  • Operating system: macOS 13.5.2
  • rustc --version: rustc 1.72.0 (5680fa18f 2023-08-23
@aldur aldur added the bug label Sep 15, 2023
@kyrias
Copy link

kyrias commented Sep 15, 2023

It seems like this dependency isn't even used anymore and so could simply be removed.

@aldur
Copy link
Contributor Author

aldur commented Sep 15, 2023

If that's the case, I could take a stab at it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants