This project might be open to known security vulnerabilities , which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom .
Crate aw-client-rust Dependencies (13 total, 5 outdated, 1 possibly insecure)
Crate Required Latest Status reqwest ^0.110.12.24out of date gethostname ^0.41.1.0out of date serde ^1.01.0.228up to date phf ^0.110.13.1out of date serde_json ^1.01.0.145up to date chrono ⚠️ ^0.40.4.42maybe insecure tokio ^1.28.21.48.0up to date rand ^0.90.9.2up to date log ^0.40.4.28up to date libc ^0.20.2.177up to date thiserror ^1.02.0.17out of date dirs ^4.06.0.0out of date fs4 ^0.130.13.1up to date
Dev dependencies (2 total, all up-to-date)
Crate Required Latest Status rocket ^0.5.0-rc.10.5.1up to date tokio-test *0.4.4up to date
Crate aw-datastore Dependencies (7 total, 1 outdated, 1 possibly insecure)
Crate aw-models Dependencies (5 total, 1 outdated, 1 possibly insecure)
Crate Required Latest Status chrono ⚠️ ^0.40.4.42maybe insecure log ^0.40.4.28up to date serde ^1.01.0.228up to date serde_json ^1.01.0.145up to date schemars ^0.81.1.0out of date
Crate aw-transform Dependencies (6 total, 1 outdated, 1 possibly insecure)
Crate Required Latest Status serde ^1.01.0.228up to date url >=2.22.5.7up to date serde_json ^1.01.0.145up to date fancy-regex ^0.12.00.16.2out of date log ^0.40.4.28up to date chrono ⚠️ ^0.40.4.42maybe insecure
Dev dependencies (1 total, 1 outdated)
Crate Required Latest Status criterion ^0.5.10.7.0out of date
Crate aw-server Dependencies (21 total, 4 outdated, 1 possibly insecure)
Crate aw-sync Dependencies (12 total, 4 outdated, 2 possibly insecure)
Crate aw-query Dependencies (6 total, 1 outdated, 1 possibly insecure)
Dev dependencies (1 total, 1 outdated)
Crate Required Latest Status criterion ^0.5.10.7.0out of 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
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.