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.
osmio(14 total, 4 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0 | 1.0.82 | up to date |
| byteorder | ^1.3.2 | 1.5.0 | up to date |
| bzip2 ⚠️ | ^0.4 | 0.4.4 | maybe insecure |
| chrono ⚠️ | ^0.4.9 | 0.4.38 | maybe insecure |
| derive_builder | ^0.10.2 | 0.20.0 | out of date |
| flate2 | ^1.0.12 | 1.0.30 | up to date |
| iter-progress | ^0.8.0 | 0.8.0 | up to date |
| protobuf | ~2.8.1 | 3.4.0 | out of date |
| quick-xml | ^0.30 | 0.31.0 | out of date |
| rusqlite | ^0.25.3 | 0.31.0 | out of date |
| separator | ^0.4.1 | 0.4.1 | up to date |
| serde | ^1.0 | 1.0.200 | up to date |
| serde_json | ^1.0 | 1.0.116 | up to date |
| xml-rs | ^0.8.0 | 0.8.20 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
No workarounds are known.
bzip2: bzip2 Denial of Service (DoS)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.