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 (6 total, 2 outdated, 1 possibly insecure)
Dev dependencies (2 total, all up-to-date)
Crate Required Latest Status rocket ^0.5.0-rc.1
0.5.1
up to date tokio-test *
0.4.4
up to date
Crate aw-datastore
Dependencies (7 total, 1 outdated, 1 possibly insecure)
Crate aw-models
Dependencies (5 total, 1 possibly insecure)
Crate Required Latest Status chrono ⚠️ ^0.4
0.4.41
maybe insecure log ^0.4
0.4.27
up to date serde ^1.0
1.0.219
up to date serde_json ^1.0
1.0.140
up to date schemars ^0.8
0.8.22
up to date
Crate aw-transform
Dependencies (6 total, 1 outdated, 1 possibly insecure)
Crate Required Latest Status serde ^1.0
1.0.219
up to date url >=2.2
2.5.4
up to date serde_json ^1.0
1.0.140
up to date fancy-regex ^0.12.0
0.14.0
out of date log ^0.4
0.4.27
up to date chrono ⚠️ ^0.4
0.4.41
maybe insecure
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status criterion ^0.5.1
0.5.1
up to date
Crate aw-server
Dependencies (21 total, 3 outdated, 1 possibly insecure)
Crate aw-sync
Dependencies (12 total, 3 outdated, 2 possibly insecure)
Crate aw-query
Dependencies (6 total, 1 outdated, 1 possibly insecure)
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status criterion ^0.5.1
0.5.1
up 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
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.