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 amadeus-aws

Dependencies

(15 total, 9 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 amadeus-core=0.1.60.4.3out of date
 amadeus-types=0.1.60.4.3out of date
 chrono ⚠️^0.40.4.38maybe insecure
 flate2^1.01.0.30up to date
 futures^0.10.3.30out of date
 http^0.21.1.0out of date
 once_cell^1.01.19.0up to date
 openssl ⚠️^0.100.10.64maybe insecure
 rusoto_core^0.420.48.0out of date
 rusoto_s3^0.420.48.0out of date
 serde^1.01.0.200up to date
 serde_closure^0.20.3.3out of date
 tokio ⚠️^0.1.71.37.0out of date
 tokio-retry^0.20.3.0out of date
 url^2.12.5.0up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-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: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.