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 nom-exif

Dependencies

(9 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.7.11.11.0up to date
 chrono ⚠️^0.40.4.43maybe insecure
 iso6709parse^0.1.01.0.0out of date
 nom^7.18.0.0out of date
 regex^1.101.12.2up to date
 serde^1.01.0.228up to date
 thiserror^2.0.112.0.18up to date
 tokio^1.40.01.49.0up to date
 tracing^0.1.400.1.44up to date

Dev dependencies

(8 total, 2 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.40.4.43maybe insecure
 clap^4.44.5.55up to date
 rand^0.90.9.2up to date
 regex^1.101.12.2up to date
 serde_json^1.01.0.149up to date
 test-case^33.3.1up to date
 tokio^1.40.01.49.0up to date
 tracing-subscriber ⚠️^0.3.180.3.22maybe insecure

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

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.