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 serde_with

Dependencies

(13 total, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.22.10.22.1up to date
 chrono^0.4.200.4.41up to date
 doc-comment^0.3.30.3.3up to date
 document-features^0.2.70.2.11up to date
 hashbrown ⚠️^0.15.00.15.3maybe insecure
 hex^0.4.30.4.3up to date
 indexmap^2.02.9.0up to date
 schemars^0.8.160.8.22up to date
 serde^1.0.1521.0.219up to date
 serde_derive^1.0.1521.0.219up to date
 serde_json^1.0.451.0.140up to date
 serde_with_macros=3.12.03.12.0up to date
 time~0.3.360.3.41up to date

Dev dependencies

(17 total, 3 outdated)

CrateRequiredLatestStatus
 expect-test^1.5.01.5.1up to date
 fnv^1.0.61.0.7up to date
 glob^0.3.00.3.2up to date
 jsonschema^0.26.10.30.0out of date
 mime^0.3.160.3.17up to date
 pretty_assertions^1.4.01.4.1up to date
 regex^1.11.01.11.1up to date
 rmp-serde^1.3.01.3.0up to date
 ron^0.80.10.1out of date
 rustversion^1.0.01.0.20up to date
 schemars^0.8.160.8.22up to date
 serde^1.0.1521.0.219up to date
 serde-xml-rs^0.6.00.8.0out of date
 serde_json^1.0.251.0.140up to date
 serde_test^1.0.1241.0.177up to date
 serde_yaml^0.9.20.9.34+deprecatedup to date
 version-sync^0.9.10.9.5up to date

Security Vulnerabilities

hashbrown: Borsh serialization of HashMap is non-canonical

RUSTSEC-2024-0402

The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding.

This can result in consensus splits and cause equivalent objects to be considered distinct.

This was patched in 0.15.1.