Skip to content
Noroxi
CVE-2023-4535· NVD / CVE Program· CNA redhat

Opensc: out-of-bounds read in myeid driver handling encryption using symmetric keys

Noroxi assessment

Priority: Monitor (action score 15/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.51% (FIRST EPSS).
  • Physical access to the device is required. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
  • Fixed version: opensc (AlmaLinux:9) 0.23.0-3.el9_3; opensc (Debian:12) 0.23.0-0.3+deb12u1; opensc (Debian:13) 0.23.0-2.

Low priority for now. Upgrade to opensc (AlmaLinux:9) 0.23.0-3.el9_3; opensc (Debian:12) 0.23.0-0.3+deb12u1; opensc (Debian:13) 0.23.0-2 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

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.

LowCVSS 3.8 · v3.1—No exploit Fix available
Published
Nov 6, 2023
Updated
Jun 17, 2026
EPSS
0.5% · 42th percentile

Report tools

JSON

Action score

15

Monitor

Low priority for now.

CVSS
15 / 40 · 3.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CNA vs NVD score

NVD
3.8
CNA · redhat
4.5
0.7 point gap

CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L

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.

Follow CVE-2023-4535

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for opensc project records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
opensc projectopensc
fedoraprojectfedora
redhatenterprise linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora38
  • fedoraproject fedora39
  • opensc project opensc0.23.0
  • redhat enterprise linux9.0

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.

  • Red Hat Red Hat Enterprise Linux 7

    • all versionsunknown

  • Red Hat Red Hat Enterprise Linux 8

    • all versionsunknown

  • Red Hat Red Hat Enterprise Linux 9

    • 0:0.23.0-3.el9_3 and laternot affected · rpm

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9openscbefore 0.23.0-3.el9_30.23.0-3.el9_3
Debian:12openscbefore 0.23.0-0.3+deb12u10.23.0-0.3+deb12u1
Debian:13openscbefore 0.23.0-20.23.0-2
openSUSE:Tumbleweedopenscbefore 0.23.0-3.10.23.0-3.1
Red Hat:enterprise_linux:9::baseosopenscbefore 0:0.23.0-3.el9_30:0.23.0-3.el9_3
Red Hat:enterprise_linux:9::baseosopensc-debuginfobefore 0:0.23.0-3.el9_30:0.23.0-3.el9_3
Red Hat:enterprise_linux:9::baseosopensc-debugsourcebefore 0:0.23.0-3.el9_30:0.23.0-3.el9_3

Same product

opensc project: all records

Other highest-scoring records for the same primary product.

  • CVE-2019-6502sc_context_create in ctx.c in libopensc in OpenSC 0.19.0 has a memory leak, as demonstrated by a call from eidenv.
    31Monitor
  • CVE-2021-34193Stack overflow vulnerability in OpenSC smart card middleware before 0.23 via crafted responses to APDUs.
    30Monitor
  • CVE-2019-16058An issue was discovered in the pam_p11 component 0.2.0 and 0.3.0 for OpenSC.
    30Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2023-40660Nov 6, 2023 · Opensc: potential pin bypass when card tracks its own login state
    26Monitor
  • ← EarlierCVE-2023-40661Nov 6, 2023 · Opensc: multiple memory issues with pkcs15-init (enrollment tool)
    25Monitor
  • Later →CVE-2023-5992Jan 31, 2024 · Opensc: side-channel leaks while stripping encryption pkcs#1 padding
    23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:opensc0.23.0-3.el9_3 · AlmaLinux:9Package registry (OSV)
debian:opensc0.23.0-0.3+deb12u1 · Debian:12Package registry (OSV)
opensuse:opensc0.23.0-3.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:opensc0:0.23.0-3.el9_3 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:opensc-debuginfo0:0.23.0-3.el9_3 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:opensc-debugsource0:0.23.0-3.el9_3 · Red Hat:enterprise_linux:9::baseosPackage 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, 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

  • Physical access to the device is required.
  • No account or password is required.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Physical
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
Low

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L

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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records