Heap disclosure and crash via swapped reply length
Published Apr 4, 2024 · Updated Nov 20, 2025
Heap buffer over-read in X.Org Server 1.12.0 through 21.1.11 allows local users to read heap data and crash XQuartz. ProcAppleDRICreatePixmap uses the byte-swapped reply length, rather than the original length, as the byte count when returning pixmap data. Exploitation requires an authorized X client with different endianness, applies only to XQuartz on macOS, and does not let the client choose which heap region is returned.
Summary
What happened
Heap buffer over-read in X.Org Server 1.12.0 through 21.1.11 allows local users to read heap data and crash XQuartz. ProcAppleDRICreatePixmap uses the byte-swapped reply length, rather than the original length, as the byte count when returning pixmap data. Exploitation requires an authorized X client with different endianness, applies only to XQuartz on macOS, and does not let the client choose which heap region is returned.
The record
- CVE
- CVE-2024-31082
- Published
- Apr 4, 2024
- Updated
- Nov 20, 2025
- Vendor
- X.Org
- Product
- X.Org Server
- Classifications
- CWE-126, T1499.004, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 4, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 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=1.12.0 <21.1.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
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