CVE-2023-43785: Libx11: out-of-bounds memory access in _xkbreadkeysyms()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.66% (FIRST EPSS); higher than 51.8% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: gitlab.freedesktop.org/xorg/lib/libx11 libX11 1.8.7.
Low priority for now. Upgrade to gitlab.freedesktop.org/xorg/lib/libx11 libX11 1.8.7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A vulnerability was found in libX11 due to a boundary condition within the _XkbReadKeySyms() function. This flaw allows a local user to trigger an out-of-bounds read error and read the contents of memory on the system.
- Published
- Oct 10, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- CWE-787
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · redhat
- 6.5
- 1.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| x.org | libx11 | cpe:2.3:a:x.org:libx11 |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora38
- redhat enterprise linux8.0
- redhat enterprise linux9.0
- x.org libx11before 1.8.7
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
gitlab.freedesktop.org/xorg/lib/libx11 libX11
- before 1.8.7affected · semver
Red Hat Red Hat Enterprise Linux 6
- all versionsunknown
Red Hat Red Hat Enterprise Linux 7
- all versionsunknown
Red Hat Red Hat Enterprise Linux 8
- 0:1.6.8-8.el8 and laternot affected · rpm
Red Hat Red Hat Enterprise Linux 9
- 0:1.7.0-9.el9 and laternot affected · rpm
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | libX11 | before 1.6.8-8.el8 | 1.6.8-8.el8 |
| AlmaLinux:8 | libX11-common | before 1.6.8-8.el8 | 1.6.8-8.el8 |
| AlmaLinux:8 | libX11-devel | before 1.6.8-8.el8 | 1.6.8-8.el8 |
| AlmaLinux:8 | libX11-xcb | before 1.6.8-8.el8 | 1.6.8-8.el8 |
| AlmaLinux:9 | libX11 | before 1.7.0-9.el9 | 1.7.0-9.el9 |
| AlmaLinux:9 | libX11-common | before 1.7.0-9.el9 | 1.7.0-9.el9 |
| AlmaLinux:9 | libX11-devel | before 1.7.0-9.el9 | 1.7.0-9.el9 |
| AlmaLinux:9 | libX11-xcb | before 1.7.0-9.el9 | 1.7.0-9.el9 |
| Alpine:v3.16 | libx11 | before 1.8.7-r0 | 1.8.7-r0 |
| Debian:10 | libx11 | before 2:1.6.7-1+deb10u4 | 2:1.6.7-1+deb10u4 |
| Debian:11 | libx11 | before 2:1.7.2-1+deb11u2 | 2:1.7.2-1+deb11u2 |
| Debian:12 | libx11 | before 2:1.8.4-2+deb12u2 | 2:1.8.4-2+deb12u2 |
| Debian:13 | libx11 | before 2:1.8.7-1 | 2:1.8.7-1 |
| openSUSE:Leap 15.4 | libX11 | before 1.6.5-150000.3.33.1 | 1.6.5-150000.3.33.1 |
| Red Hat:enterprise_linux:8::appstream | libX11 | before 0:1.6.8-8.el8 | 0:1.6.8-8.el8 |
| Red Hat:enterprise_linux:8::appstream | libX11-common | before 0:1.6.8-8.el8 | 0:1.6.8-8.el8 |
| Red Hat:enterprise_linux:8::appstream | libX11-debuginfo | before 0:1.6.8-8.el8 | 0:1.6.8-8.el8 |
| Red Hat:enterprise_linux:8::appstream | libX11-debugsource | before 0:1.6.8-8.el8 | 0:1.6.8-8.el8 |
| Red Hat:enterprise_linux:8::appstream | libX11-devel | before 0:1.6.8-8.el8 | 0:1.6.8-8.el8 |
| Red Hat:enterprise_linux:8::appstream | libX11-xcb | before 0:1.6.8-8.el8 | 0:1.6.8-8.el8 |
| Red Hat:enterprise_linux:8::appstream | libX11-xcb-debuginfo | before 0:1.6.8-8.el8 | 0:1.6.8-8.el8 |
| Red Hat:enterprise_linux:9::appstream | libX11 | before 0:1.7.0-9.el9 | 0:1.7.0-9.el9 |
| Red Hat:enterprise_linux:9::appstream | libX11-common | before 0:1.7.0-9.el9 | 0:1.7.0-9.el9 |
| Red Hat:enterprise_linux:9::appstream | libX11-debuginfo | before 0:1.7.0-9.el9 | 0:1.7.0-9.el9 |
+8
Same product
x.org: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-31535LookupCol.c in X.Org X through X11R7.7 and libX11 before 1.7.1 might allow remote attackers to execute arbitrary code.42Plan
- CVE-2018-14600An issue was discovered in libX11 through 1.6.5.42Plan
- CVE-2018-14599An issue was discovered in libX11 through 1.6.5.40Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-14363Sep 11, 2020 · An integer overflow vulnerability leading to a double-free was found in libX11.31Monitor
- ← EarlierCVE-2023-3138Jun 28, 2023 · A vulnerability was found in libX11.30Monitor
- Later →CVE-2023-43786Oct 10, 2023 · Libx11: stack exhaustion from infinite recursion in putsubimage()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| gitlab.freedesktop.org/xorg/lib/libx11 libX11 | 1.8.7 | Vendor (CNA) |
| almalinux:libX11 | 1.7.0-9.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:libX11-common | 1.7.0-9.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:libX11-devel | 1.7.0-9.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:libX11-xcb | 1.7.0-9.el9 · AlmaLinux:9 | Package registry (OSV) |
| alpine:libx11 | 1.8.7-r0 · Alpine:v3.16 | Package registry (OSV) |
| debian:libx11 | 2:1.8.4-2+deb12u2 · Debian:12 | Package registry (OSV) |
| opensuse:libX11 | 1.6.5-150000.3.33.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:libX11 | 0:1.7.0-9.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libX11-common | 0:1.7.0-9.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libX11-debuginfo | 0:1.7.0-9.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libX11-debugsource | 0:1.7.0-9.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libX11-devel | 0:1.7.0-9.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libX11-xcb | 0:1.7.0-9.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libX11-xcb-debuginfo | 0:1.7.0-9.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:libX11 | 0:1.7.0-9.el9 · Rocky Linux:9 | Package registry (OSV) |
| suse:libX11 | 1.6.5-150000.3.33.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.