Loading vulnerability details...
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:
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.
tracing-subscriber version 0.3.20 fixes this vulnerability by escaping ANSI control characters in when writing events to destinations that may be printed to the terminal.
Avoid printing logs to terminal emulators without escaping ANSI control sequences.
https://www.packetlabs.net/posts/weaponizing-ansi-escape-sequences/
We would like to thank zefr0x who responsibly reported the issue at security@tokio.rs.
If you believe you have found a security vulnerability in any tokio-rs project, please email us at security@tokio.rs.
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:
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.
tracing-subscriber version 0.3.20 fixes this vulnerability by escaping ANSI control characters in when writing events to destinations that may be printed to the terminal.
Avoid printing logs to terminal emulators without escaping ANSI control sequences.
https://www.packetlabs.net/posts/weaponizing-ansi-escape-sequences/
We would like to thank zefr0x who responsibly reported the issue at security@tokio.rs.
If you believe you have found a security vulnerability in any tokio-rs project, please email us at security@tokio.rs.
This medium-severity vulnerability could be exploited under certain conditions to compromise security controls or access sensitive information. Should be addressed in a timely manner.
Probability of exploitation in the next 30 days · more likely than 23.6% of all CVEs.
Apply security patches to version 0.3.20 immediately
Isolate affected systems from untrusted networks until patching is complete
Implement enhanced monitoring for exploitation attempts and unusual behavior