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 address Dependencies (2 total, 1 outdated)
Crate Required Latest Status hex ^0.4.30.4.3up to date sha2 ^0.10.60.11.0out of date
Crate api Dependencies (2 total, all up-to-date)
Crate Required Latest Status serde ^1.0.1631.0.228up to date hex ^0.4.30.4.3up to date
Crate block Dependencies (4 total, 1 outdated)
Dev dependencies (1 total, 1 outdated)
Crate Required Latest Status bincode ^1.3.33.0.0out of date
Crate blockchain Dependencies (10 total, 5 outdated)
Crate Required Latest Status rocksdb ^0.21.00.24.0out of date colored ^2.0.03.1.1out of date tracing ^0.1.370.1.44up to date hex ^0.4.30.4.3up to date serde ^1.0.1631.0.228up to date lazy_static ^1.4.01.5.0up to date bincode ^1.3.33.0.0out of date chrono ^0.4.260.4.44up to date uint ^0.9.50.10.0out of date sha2 ^0.10.60.11.0out of date
Crate control Dependencies (4 total, 2 outdated, 1 possibly insecure)
Crate db Dependencies (6 total, 2 outdated)
Crate encryption Dependencies (4 total, 1 outdated)
Dev dependencies (1 total, 1 outdated)
Crate Required Latest Status rand ^0.8.50.10.0out of date
Crate fork Dependencies (7 total, 4 outdated)
Crate Required Latest Status rocksdb ^0.21.00.24.0out of date tracing ^0.1.370.1.44up to date hex ^0.4.30.4.3up to date serde ^1.0.1631.0.228up to date bincode ^1.3.33.0.0out of date uint ^0.9.50.10.0out of date sha2 ^0.10.60.11.0out of date
Crate key Dependencies (4 total, 3 outdated)
Crate Required Latest Status secp256k1 ^0.27.00.31.1out of date vrf ^0.2.40.2.5up to date rand ^0.8.50.10.0out of date sha2 ^0.10.60.11.0out of date
Crate key-store Dependencies (3 total, 1 outdated)
Crate Required Latest Status hex ^0.4.30.4.3up to date lazy_static ^1.4.01.5.0up to date rand_core ^0.6.40.10.0out of date
Crate multiaddr Dependencies (1 total, 1 outdated)
Crate Required Latest Status libp2p ^0.51.30.56.0out of date
Crate p2p Dependencies (10 total, 3 outdated)
Crate Required Latest Status tracing ^0.1.370.1.44up to date serde ^1.0.1631.0.228up to date void ^1.0.21.0.2up to date tokio ^1.28.11.51.0up to date sha2 ^0.10.60.11.0out of date rand ^0.8.50.10.0out of date chrono ^0.4.240.4.44up to date libp2p ^0.51.30.56.0out of date async-trait ^0.1.680.1.89up to date futures ^0.3.280.3.32up to date
Crate tofuri Dependencies (20 total, 8 outdated, 1 possibly insecure)
Crate stake Dependencies (3 total, 1 outdated)
Crate Required Latest Status serde ^1.0.1631.0.228up to date serde-big-array ^0.5.10.5.1up to date sha2 ^0.10.60.11.0out of date
Dev dependencies (1 total, 1 outdated)
Crate Required Latest Status bincode ^1.3.33.0.0out of date
Crate sync Dependencies (2 total, all up-to-date)
Crate Required Latest Status serde ^1.0.1631.0.228up to date lazy_static ^1.4.01.5.0up to date
Crate transaction Dependencies (3 total, 1 outdated)
Crate Required Latest Status serde ^1.0.1631.0.228up to date serde-big-array ^0.5.10.5.1up to date sha2 ^0.10.60.11.0out of date
Dev dependencies (1 total, 1 outdated)
Crate Required Latest Status bincode ^1.3.33.0.0out of date
Crate tree Dependencies (2 total, all up-to-date)
Crate Required Latest Status serde ^1.0.1641.0.228up to date hex ^0.4.30.4.3up to date
Crate vanity Dependencies (4 total, 1 possibly insecure)
Crate wallet Dependencies (12 total, 6 outdated)
Crate Required Latest Status inquire ^0.6.20.9.4out of date colored ^2.0.03.1.1out of date zxcvbn ^2.2.23.1.0out of date chrono ^0.4.240.4.44up to date hex ^0.4.30.4.3up to date crossterm ^0.26.10.29.0out of date tracing ^0.1.370.1.44up to date tokio ^1.28.11.51.0up to date clap ^4.2.74.6.0up to date rand ^0.8.50.10.0out of date lazy_static ^1.4.01.5.0up to date reqwest ^0.11.180.13.2out of date
Security Vulnerabilities tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequencesRUSTSEC-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.
