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 openapi-fuzzer

Dependencies

(13 total, 6 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 argh^0.1.40.1.13up to date
 url^2.2.02.5.8up to date
 anyhow^1.0.371.0.100up to date
 openapiv3^0.5.02.2.0out of date
 serde^1.01.0.228up to date
 serde_yaml ⚠️^0.80.9.34+deprecatedout of date
 ureq^2.7.03.1.4out of date
 rustls ⚠️^0.210.23.36out of date
 openapi_utils^0.2.20.6.1out of date
 arbitrary^11.4.2up to date
 serde_json^1.01.0.149up to date
 proptest^1.1.01.9.0up to date
 indexmap^1.9.12.13.0out of date

Security Vulnerabilities

serde_yaml: Uncontrolled recursion leads to abort in deserialization

RUSTSEC-2018-0005

Affected versions of this crate did not properly check for recursion while deserializing aliases.

This allows an attacker to make a YAML file with an alias referring to itself causing an abort.

The flaw was corrected by checking the recursion depth.

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.