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 lopdf

Dependencies

(19 total, 2 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 aes^0.8.40.8.4up to date
 cbc^0.1.20.1.2up to date
 chrono ⚠️^0.40.4.44maybe insecure
 encoding_rs^0.8.320.8.35up to date
 flate2^1.01.1.9up to date
 image^0.250.25.10up to date
 indexmap^2.2.32.13.0up to date
 itoa^1.01.0.17up to date
 log^0.40.4.29up to date
 md-5^0.100.10.6up to date
 nom^7.18.0.0out of date
 nom_locate^4.2.05.0.0out of date
 rangemap^1.51.7.1up to date
 rayon^1.61.11.0up to date
 serde^1.01.0.228up to date
 thiserror^2.0.32.0.18up to date
 time ⚠️^0.30.3.47maybe insecure
 tokio ⚠️^11.50.0maybe insecure
 weezl^0.10.1.12up to date

Dev dependencies

(5 total, all up-to-date)

CrateRequiredLatestStatus
 clap^4.04.6.0up to date
 env_logger^0.110.11.9up to date
 serde_json^1.01.0.149up to date
 shellexpand^3.03.1.2up to date
 tempfile^3.33.27.0up 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

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);

time: Denial of Service via Stack Exhaustion

RUSTSEC-2026-0009

Impact

When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.

Patches

A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.

Workarounds

Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.