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 rpki

Dependencies

(14 total, 8 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 base64^0.10.10.22.1out of date
 bcder ⚠️^0.4.00.7.4out of date
 bytes^0.4.121.6.0out of date
 chrono ⚠️^0.4.70.4.38maybe insecure
 derive_more^0.15.00.99.17out of date
 log^0.4.70.4.21up to date
 openssl ⚠️^0.10.230.10.64maybe insecure
 quick-xml^0.16.10.31.0out of date
 ring^0.14.60.17.8out of date
 serde^1.0.951.0.200up to date
 slab^0.4.20.4.9up to date
 untrusted^0.6.20.9.0out of date
 unwrap^1.2.11.2.1up to date
 uuid^0.7.41.8.0out of date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 serde_json^1.0.401.0.116up 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

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.

bcder: BER/CER/DER decoder panics on invalid input

RUSTSEC-2023-0062

Due to insufficient checking of input data, decoding certain data sequences can lead to bcder panicking rather than returning an error. This can affect both the actual decoding stage as well as accessing content of types that utilized delayed decoding.

bcder 0.7.3 fixes these issues by more thoroughly checking inputs and returning errors as expected.