This project contains known security vulnerabilities . Find detailed information at the bottom .
Crate sqlx Dev dependencies (17 total, 4 outdated, 1 possibly insecure)
Crate sqlx-test Dependencies (3 total, all up-to-date)
Crate Required Latest Status env_logger ^0.110.11.8up to date dotenvy ^0.15.00.15.7up to date anyhow ^1.0.261.0.100up to date
Crate sqlx-core Dependencies (32 total, 2 outdated)
Dev dependencies (1 total, 1 possibly insecure)
Crate Required Latest Status tokio ⚠️ ^11.48.0maybe insecure
Crate sqlx-macros Dependencies (3 total, all up-to-date)
Crate Required Latest Status proc-macro2 ^1.0.361.0.103up to date syn ^2.0.522.0.108up to date quote ^1.0.261.0.41up to date
Crate sqlx-macros-core Dependencies (10 total, all up-to-date)
Crate Required Latest Status hex ^0.4.30.4.3up to date heck ^0.50.5.0up to date either ^1.6.11.15.0up to date proc-macro2 ^1.0.791.0.103up to date serde ^1.0.1321.0.228up to date serde_json ^1.0.731.0.145up to date sha2 ^0.10.00.10.9up to date syn ^2.0.522.0.108up to date quote ^1.0.261.0.41up to date url ^2.2.22.5.7up to date
Crate sqlx-cli Dependencies (15 total, 3 outdated, 3 possibly insecure)
Dev dependencies (2 total, all up-to-date)
Crate Required Latest Status assert_cmd ^2.0.112.0.17up to date tempfile ^3.10.13.23.0up to date
Crate sqlx-mysql Dependencies (30 total, 2 outdated, 1 insecure, 1 possibly insecure)
Crate sqlx-postgres Dependencies (26 total, 1 outdated, 1 possibly insecure)
Crate sqlx-sqlite Dependencies (15 total, all up-to-date)
Crate sqlx-example-mysql-todos Dependencies (3 total, 1 possibly insecure)
Crate Required Latest Status anyhow ^1.01.0.100up to date clap ^44.5.50up to date tokio ⚠️ ^1.20.01.48.0maybe insecure
Crate sqlx-example-postgres-axum-social Dependencies (14 total, 5 outdated, 1 possibly insecure)
Crate Required Latest Status axum ^0.5.130.8.6out of date tokio ⚠️ ^1.20.11.48.0maybe insecure argon2 ^0.4.10.5.3out of date rand ^0.8.50.9.2out of date regex ^1.6.01.12.2up to date serde ^1.0.1401.0.228up to date serde_with ^2.0.03.15.1out of date time ^0.3.110.3.44up to date uuid ^1.1.21.18.1up to date validator ^0.16.00.20.0out of date anyhow ^1.0.581.0.100up to date dotenvy ^0.15.10.15.7up to date thiserror ^2.0.02.0.17up to date tracing ^0.1.350.1.41up to date
Dev dependencies (2 total, 1 outdated)
Crate Required Latest Status serde_json ^1.0.821.0.145up to date tower ^0.4.130.5.2out of date
Crate sqlx-example-postgres-chat Dependencies (4 total, 3 outdated, 1 possibly insecure)
Crate sqlx-example-postgres-files Dependencies (3 total, 1 possibly insecure)
Crate Required Latest Status anyhow ^1.01.0.100up to date tokio ⚠️ ^1.20.01.48.0maybe insecure dotenvy ^0.15.00.15.7up to date
Crate sqlx-example-postgres-json Dependencies (6 total, 1 possibly insecure)
Crate Required Latest Status anyhow ^1.01.0.100up to date dotenvy ^0.15.00.15.7up to date serde ^11.0.228up to date serde_json ^11.0.145up to date clap ^44.5.50up to date tokio ⚠️ ^1.20.01.48.0maybe insecure
Crate sqlx-example-postgres-listen Dependencies (2 total, 1 possibly insecure)
Crate Required Latest Status futures-util ^0.3.10.3.31up to date tokio ⚠️ ^1.20.01.48.0maybe insecure
Crate sqlx-example-postgres-mockable-todos Dependencies (6 total, 1 outdated, 1 possibly insecure)
Crate sqlx-example-postgres-multi-database Dependencies (6 total, 1 outdated, 1 possibly insecure)
Crate sqlx-example-postgres-multi-tenant Dependencies (6 total, 1 outdated, 1 possibly insecure)
Crate sqlx-example-postgres-preferred-crates Dependencies (4 total, 1 possibly insecure)
Crate Required Latest Status anyhow ^11.0.100up to date chrono ⚠️ ^0.40.4.42maybe insecure serde ^11.0.228up to date uuid ^11.18.1up to date
Crate sqlx-example-postgres-todos Dependencies (4 total, 1 possibly insecure)
Crate Required Latest Status anyhow ^1.01.0.100up to date clap ^44.5.50up to date tokio ⚠️ ^1.20.01.48.0maybe insecure dotenvy ^0.15.00.15.7up to date
Crate sqlx-example-postgres-transaction Dependencies (1 total, 1 possibly insecure)
Crate Required Latest Status tokio ⚠️ ^1.20.01.48.0maybe insecure
Crate sqlx-example-sqlite-todos Dependencies (3 total, 1 possibly insecure)
Crate Required Latest Status anyhow ^1.01.0.100up to date clap ^44.5.50up to date tokio ⚠️ ^1.20.01.48.0maybe insecure
Crate sqlx-example-sqlite-extension Dependencies (2 total, 1 possibly insecure)
Crate Required Latest Status tokio ⚠️ ^1.20.01.48.0maybe insecure anyhow ^1.01.0.100up to date
Crate sqlx-example-postgres-multi-database-accounts Dependencies (8 total, 2 outdated, 1 possibly insecure)
Crate sqlx-example-postgres-multi-database-payments Dependencies (3 total, all up-to-date)
Crate Required Latest Status rust_decimal ^1.36.01.39.0up to date time ^0.3.370.3.44up to date uuid ^1.12.11.18.1up to date
Crate sqlx-example-postgres-multi-tenant-accounts Dependencies (8 total, 2 outdated, 1 possibly insecure)
Crate sqlx-example-postgres-multi-tenant-payments Dependencies (3 total, all up-to-date)
Crate Required Latest Status rust_decimal ^1.36.01.39.0up to date time ^0.3.370.3.44up to date uuid ^1.12.11.18.1up to date
Crate sqlx-example-postgres-preferred-crates-uses-rust-decimal Dependencies (3 total, 1 possibly insecure)
Crate sqlx-example-postgres-preferred-crates-uses-time Dependencies (3 total, all up-to-date)
Crate Required Latest Status serde ^11.0.228up to date time ^0.30.3.44up to date uuid ^11.18.1up to date
Security Vulnerabilities chrono: Potential segfault in `localtime_r` invocationsRUSTSEC-2020-0159
Impact
Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
Workarounds
No workarounds are known.
References
tokio: reject_remote_clients Configuration corruptionRUSTSEC-2023-0001
On Windows, configuring a named pipe server with pipe_mode will force ServerOptions ::reject_remote_clients as false.
This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.
The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.
Workarounds
Ensure that pipe_mode is set first after initializing a ServerOptions . For example:
let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);
Patched
>=1.18.4, <1.19.0
>=1.20.3, <1.21.0
>=1.23.1
rsa: Marvin Attack: potential key recovery through timing sidechannelsRUSTSEC-2023-0071
Impact
Due to a non-constant-time implementation, information about the private key is leaked through timing information which is observable over the network. An attacker may be able to use that information to recover the key.
Patches
No patch is yet available, however work is underway to migrate to a fully constant-time implementation.
Workarounds
The only currently available workaround is to avoid using the rsa crate in settings where attackers are able to observe timing information, e.g. local use on a non-compromised computer is fine.
References
This vulnerability was discovered as part of the "Marvin Attack ", which revealed several implementations of RSA including OpenSSL had not properly mitigated timing sidechannel attacks.
whoami: Stack buffer overflow with whoami on several Unix platformsRUSTSEC-2024-0020
With versions of the whoami crate >= 0.5.3 and < 1.5.0, calling any of these functions leads to an
immediate stack buffer overflow on illumos and Solaris:
whoami::username
whoami::realname
whoami::username_os
whoami::realname_os
With versions of the whoami crate >= 0.5.3 and < 1.0.1, calling any of the above functions also
leads to a stack buffer overflow on these platforms:
Bitrig
DragonFlyBSD
FreeBSD
NetBSD
OpenBSD
This occurs because of an incorrect definition of the passwd struct on those platforms.
As a result of this issue, denial of service and data corruption have both been observed in the
wild. The issue is possibly exploitable as well.
This vulnerability also affects other Unix platforms that aren't Linux or macOS.
This issue has been addressed in whoami 1.5.0.
For more information, see this GitHub issue .
openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`RUSTSEC-2025-0022
When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.
In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).
The maintainers thank quitbug for reporting this vulnerability to us.