CVE-2023-3138
Last modified
CVE-2023-3138 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. A vulnerability was found in libX11. The security flaw occurs because the functions in src/InitExt.c in libX11 do not check that the values provided for the Request, Event, or Error IDs are within the bounds of the arrays that those functions write to, using those IDs as array indexes. EPSS estimates a 1.66% chance of exploitation in the next 30 days.
Description
A vulnerability was found in libX11. The security flaw occurs because the functions in src/InitExt.c in libX11 do not check that the values provided for the Request, Event, or Error IDs are within the bounds of the arrays that those functions write to, using those IDs as array indexes. They trust that they were called with values provided by an Xserver adhering to the bounds specified in the X11 protocol, as all X servers provided by X.Org do. As the protocol only specifies a single byte for these values, an out-of-bounds value provided by a malicious server (or a malicious proxy-in-the-middle) can only overwrite other portions of the Display structure and not write outside the bounds of the Display structure itself, possibly causing the client to crash with this memory corruption.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| X.Org | Libx11 | < 1.8.6 |
| Redhat | Enterprise Linux | 8.0 |
| Redhat | Enterprise Linux | 9.0 |
References
- https://access.redhat.com/security/cve/CVE-2023-3138Third Party Advisory
- https://lists.x.org/archives/xorg-announce/2023-June/003406.htmlMailing List, Patch
- https://lists.x.org/archives/xorg-announce/2023-June/003407.htmlMailing List, Patch
- https://access.redhat.com/security/cve/CVE-2023-3138Third Party Advisory
- https://lists.x.org/archives/xorg-announce/2023-June/003406.htmlMailing List, Patch
- https://lists.x.org/archives/xorg-announce/2023-June/003407.htmlMailing List, Patch
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-3138?
How severe is CVE-2023-3138?
How do I fix CVE-2023-3138?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-3136The MailArchiver plugin for WordPress is vulnerable to Store…6.1
- CVE-2023-31360Incorrect default permissions in the AMD Integrated Manageme…7.3
- CVE-2023-31361A DLL hijacking vulnerability in AMD Integrated Management T…7.3
- CVE-2023-31364Improper handling of direct memory writes in the input-outpu…8.3
- CVE-2023-31365An integer overflow in the SMU could allow a privileged atta…3.9
- CVE-2023-31366Improper input validation in AMD μProf could allow an attack…5.5
- CVE-2023-3139The Protect WP Admin WordPress plugin before 4.0 discloses t…6.1
- CVE-2023-3140Missing HTTP headers (X-Frame-Options, Content-Security-Poli…4.3
- CVE-2023-31403SAP Business One installation - version 10.0, does not perfo…8
- CVE-2023-31404Under certain conditions, SAP BusinessObjects Business Intel…5
- CVE-2023-31405SAP NetWeaver AS for Java - versions ENGINEAPI 7.50, SERVERC…5.3
- CVE-2023-31406Due to insufficient input validation, SAP BusinessObjects Bu…6.1
Are you affected by CVE-2023-3138?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
