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 osmio

Dependencies

(14 total, 5 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.98up to date
 byteorder^1.3.21.5.0up to date
 bzip2 ⚠️^0.40.6.0out of date
 chrono ⚠️^0.4.90.4.41maybe insecure
 derive_builder^0.10.20.20.2out of date
 flate2^1.0.121.1.2up to date
 iter-progress^0.8.00.8.0up to date
 protobuf ⚠️~2.8.13.7.2out of date
 quick-xml^0.300.38.0out of date
 rusqlite^0.25.30.36.0out of date
 separator^0.4.10.4.1up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 xml-rs^0.8.00.8.26up 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

bzip2: bzip2 Denial of Service (DoS)

RUSTSEC-2023-0004

Working with specific payloads can cause a Denial of Service (DoS) vector.

Both Decompress and Compress implementations can enter into infinite loops given specific payloads entered that trigger it.

The issue is described in great detail in the bzip2 repository issue.

Thanks to bjrjk for finding and providing the patch for the issue and the maintainer responsibly responding to release a fix quickly.

Users who use the crate with untrusted data should update the bzip2 to 0.4.4.

protobuf: Crash due to uncontrolled recursion in protobuf crate

RUSTSEC-2024-0437

Affected version of this crate did not properly parse unknown fields when parsing a user-supplied input.

This allows an attacker to cause a stack overflow when parsing the mssage on untrusted data.