Terminal crash via out-of-bounds Sixel pixel write
Published Jan 31, 2022 · Updated Aug 3, 2024
Buffer overflow in xterm through Patch 370 allows local users to crash the terminal by displaying crafted text with Sixel enabled. set_sixel calculates a graphics-buffer offset from Sixel coordinates without rejecting out-of-bounds positions, then writes beyond the allocated buffer. The terminal must be built with Sixel support, configured to interpret Sixel graphics, and induced to process the crafted text; the demonstrated result is a SIGSEGV crash.
Summary
What happened
Buffer overflow in xterm through Patch 370 allows local users to crash the terminal by displaying crafted text with Sixel enabled. set_sixel calculates a graphics-buffer offset from Sixel coordinates without rejecting out-of-bounds positions, then writes beyond the allocated buffer. The terminal must be built with Sixel support, configured to interpret Sixel graphics, and induced to process the crafted text; the demonstrated result is a SIGSEGV crash.
The record
- CVE
- CVE-2022-24130
- Published
- Jan 31, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 31, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
Weakness, pattern, technique
Public exploit references
- Crafted Sixel crash demonstrationproof of concept · demonstrated
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