CVE-2023-4535: Red Hat Enterprise Linux 9 · Out-of-bounds Read
Affects Red Hat Enterprise Linux 9Source CVE Database V5
Not known to be exploited · CVSS 4.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
1. Monitor for and restrict physical access to critical systems, especially those using smart cards or USB tokens for authentication. 2. Implement strict device control policies to prevent unauthorized USB devices from connecting to sensitive systems. 3. Apply vendor patches and updates promptly once available from Red Hat or OpenSC maintainers. 4. Employ endpoint security solutions capable of detecting anomalous device interactions or malformed APDU communications. 5. Conduct regular audits of hardware token usage and access logs to identify suspicious activity. 6. Consider additional layers of authentication or encryption that do not solely rely on vulnerable hardware drivers. 7. Educate staff on the risks of physical device insertion and enforce policies against connecting untrusted devices. 8. Use hardware security modules (HSMs) or alternative cryptographic solutions where feasible to reduce reliance on vulnerable drivers.
Description
An out-of-bounds read vulnerability was found in OpenSC packages within the MyEID driver when handling symmetric key encryption. Exploiting this flaw requires an attacker to have physical access to the computer and a specially crafted USB device or smart card. This flaw allows the attacker to manipulate APDU responses and potentially gain unauthorized access to sensitive data, compromising the system's security.
References
- access.redhat.com/errata/RHSA-2023:7879 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2023-4535 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2240914 (opens in a new tab)
- github.com/OpenSC/OpenSC/commit/f1993dc4e0b33050b8f72a3558ee88b24c4063b2 (opens in a new tab)
- github.com/OpenSC/OpenSC/issues/2792 (opens in a new tab)
- github.com/OpenSC/OpenSC/releases/tag/0.24.0-rc1 (opens in a new tab)
- github.com/OpenSC/OpenSC/wiki/OpenSC-security-advisories (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3CPQOMCDWFRBMEFR5VK4N5MMXXU42ODE/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GLYEFIBBA37TK3UNMZN5NOJ7IWCIXLQP/ (opens in a new tab)