Screen crash via OSC 49 out-of-bounds write
Published Feb 24, 2020 · Updated Aug 4, 2024
Buffer overflow in GNU Screen before 4.8.0 allows remote attackers to crash Screen or achieve unspecified impact via crafted OSC 49 output. The OSC 49 handler divides the escape code by ten and uses the result as an index into a four-entry w_xtermosc table, writing past its bounds and corrupting memory. Exploitation requires a Screen session to process attacker-controlled terminal output; the documented consequence is process crash, while further confidentiality or integrity impact remains unspecified.
Summary
What happened
Buffer overflow in GNU Screen before 4.8.0 allows remote attackers to crash Screen or achieve unspecified impact via crafted OSC 49 output. The OSC 49 handler divides the escape code by ten and uses the result as an index into a four-entry w_xtermosc table, writing past its bounds and corrupting memory. Exploitation requires a Screen session to process attacker-controlled terminal output; the documented consequence is process crash, while further confidentiality or integrity impact remains unspecified.
The record
- CVE
- CVE-2020-9366
- Published
- Feb 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo