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 calcard

Dependencies

(11 total, 1 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.8.110.8.12up to date
 chrono^0.4.400.4.44up to date
 chrono-tz^0.10.30.10.4up to date
 hashify^0.2.70.2.9up to date
 jmap-tools^0.10.1.4up to date
 mail-builder^0.40.4.4up to date
 mail-parser^0.110.11.2up to date
 rkyv ⚠️^0.80.8.15maybe insecure
 serde^1.01.0.228up to date
 serde_json^1.01.0.149up to date
 uuid^1.191.23.0up to date

Dev dependencies

(4 total, 2 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.40.4.44maybe insecure
 rkyv ⚠️^0.80.8.15maybe insecure
 serde^1.01.0.228up to date
 serde_json^1.01.0.149up 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

rkyv: Potential Undefined Behaviors in `Arc<T>`/`Rc<T>` impls of `from_value` on OOM

RUSTSEC-2026-0001

The SharedPointer::alloc implementation for sync::Arc<T> and rc::Rc<T> in rkyv/src/impls/alloc/rc/atomic.rs (and rc.rs) does not check if the allocator returns a null pointer on OOM (Out of Memory).

This null pointer can flow through to SharedPointer::from_value, which calls Box::from_raw(ptr) with the null pointer. This triggers undefined behavior when utilizing safe deserialization APIs (such as rkyv::from_bytes or rkyv::deserialize_using) if an OOM condition occurs during the allocation of the shared pointer.

The issue is reachable through safe code and violates Rust's safety guarantees.