Memory disclosure via corrupted XPM colormap
Published Oct 12, 2023 · Updated Nov 6, 2025
Out-of-bounds read in X.Org libXpm before 3.5.17 allows local users to disclose process memory through a crafted XPM colormap. The X.Org advisory states that the corrupted colormap causes the read but does not identify the parser function or unchecked operation. An application must open the attacker-supplied XPM file; the flaw reads adjacent memory without changing data or interrupting service.
Summary
What happened
Out-of-bounds read in X.Org libXpm before 3.5.17 allows local users to disclose process memory through a crafted XPM colormap. The X.Org advisory states that the corrupted colormap causes the read but does not identify the parser function or unchecked operation. An application must open the attacker-supplied XPM file; the flaw reads adjacent memory without changing data or interrupting service.
The record
- CVE
- CVE-2023-43789
- Published
- Oct 12, 2023
- Updated
- Nov 6, 2025
- Vendor
- X.Org
- Product
- libXpm
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 12, 2023CVE publishedPublication date reported by the CVE source.
- Nov 6, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.5.17
What conditions does exploitation require?
What is affected?
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
- X.Org corrupted-colormap test inputproof 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