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 javelin

Dependencies

(19 total, 12 outdated, 4 possibly insecure)

CrateRequiredLatestStatus
 bytes^0.41.6.0out of date
 chrono ⚠️^0.40.4.37maybe insecure
 clap~2.324.5.4out of date
 futures^0.10.3.30out of date
 javelin-codec^0.3.40.3.4up to date
 log^0.40.4.21up to date
 m3u8-rs^1.06.0.0out of date
 mpeg2ts^0.10.3.1out of date
 native-tls^0.20.2.11up to date
 parking_lot^0.70.12.1out of date
 rml_rtmp^0.20.8.0out of date
 serde^1.01.0.197up to date
 serde_json^1.01.0.115up to date
 serde_yaml ⚠️^0.80.9.34+deprecatedout of date
 simplelog^0.50.12.2out of date
 tempfile^3.03.10.1up to date
 tokio ⚠️^0.11.36.0out of date
 tokio-tls^0.20.3.1out of date
 warp ⚠️^0.10.3.6out 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.

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.

warp: Improper validation of Windows paths could lead to directory traversal attack

RUSTSEC-2022-0082

Path resolution in warp::filters::fs::dir didn't correctly validate Windows paths meaning paths like /foo/bar/c:/windows/web/screen/img101.png would be allowed and respond with the contents of c:/windows/web/screen/img101.png. Thus users could potentially read files anywhere on the filesystem.

This only impacts Windows. Linux and other unix likes are not impacted by this.