A vulnerbility was found in OpenSC.
Noroxi assessment
Priority: Monitor (action score 28/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.29% (FIRST EPSS).
- 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: opensc (AlmaLinux:8) 0.20.0-6.el8; opensc (AlmaLinux:9) 0.23.0-2.el9; opensc (Debian:10) 0.19.0-1+deb10u2.
Low priority for now. Upgrade to opensc (AlmaLinux:8) 0.20.0-6.el8; opensc (AlmaLinux:9) 0.23.0-2.el9; opensc (Debian:10) 0.19.0-1+deb10u2 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 vulnerbility was found in OpenSC. This security flaw cause a buffer overrun vulnerability in pkcs15 cardos_have_verifyrc_package. The attacker can supply a smart card package with malformed ASN1 context. The cardos_have_verifyrc_package function scans the ASN1 buffer for 2 tags, where remaining length is wrongly caculated due to moved starting pointer. This leads to possible heap-based buffer oob read. In cases where ASAN is enabled while compiling this causes a crash. Further info leak or more damage is possible.
- Published
- May 31, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-119
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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 |
|---|---|---|
| opensc project | opensc | cpe:2.3:a:opensc_project:opensc |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- opensc project opensc0.23.0
- redhat enterprise linux8.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.
n/a OpenSC
- opensc-0.23.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | opensc | before 0.20.0-6.el8 | 0.20.0-6.el8 |
| AlmaLinux:9 | opensc | before 0.23.0-2.el9 | 0.23.0-2.el9 |
| Debian:10 | opensc | before 0.19.0-1+deb10u2 | 0.19.0-1+deb10u2 |
| Debian:11 | opensc | before 0.21.0-1+deb11u1 | 0.21.0-1+deb11u1 |
| Debian:12 | opensc | before 0.23.0-0.3 | 0.23.0-0.3 |
| openSUSE:Leap Micro 5.3 | opensc | before 0.22.0-150400.3.3.1 | 0.22.0-150400.3.3.1 |
| openSUSE:Tumbleweed | opensc | before 0.23.0-2.1 | 0.23.0-2.1 |
| Red Hat:enterprise_linux:8::baseos | opensc | before 0:0.20.0-6.el8 | 0:0.20.0-6.el8 |
| Red Hat:enterprise_linux:8::baseos | opensc-debuginfo | before 0:0.20.0-6.el8 | 0:0.20.0-6.el8 |
| Red Hat:enterprise_linux:8::baseos | opensc-debugsource | before 0:0.20.0-6.el8 | 0:0.20.0-6.el8 |
| Red Hat:enterprise_linux:9::baseos | opensc | before 0:0.23.0-2.el9 | 0:0.23.0-2.el9 |
| Red Hat:enterprise_linux:9::baseos | opensc-debuginfo | before 0:0.23.0-2.el9 | 0:0.23.0-2.el9 |
| Red Hat:enterprise_linux:9::baseos | opensc-debugsource | before 0:0.23.0-2.el9 | 0:0.23.0-2.el9 |
| SUSE:Linux Enterprise Micro 5.3 | opensc | before 0.22.0-150400.3.3.1 | 0.22.0-150400.3.3.1 |
| SUSE:Linux Enterprise Real Time 15 SP3 | opensc | before 0.19.0-150100.3.22.1 | 0.19.0-150100.3.22.1 |
| SUSE:Linux Enterprise Server 12 SP5 | opensc | before 0.13.0-3.22.1 | 0.13.0-3.22.1 |
Same product
opensc project: all recordsOther 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-2021-42781Apr 18, 2022 · Heap buffer overflow issues were found in Opensc before version 0.22.0 in pkcs15-oberthur.c that could potentially crash programs using the 22Monitor
- ← EarlierCVE-2021-42782Apr 18, 2022 · Stack buffer overflow issues were found in Opensc before version 0.22.0 in various places that could potentially crash programs using the li22Monitor
- Later →CVE-2023-40660Nov 6, 2023 · Opensc: potential pin bypass when card tracks its own login state26Monitor
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 |
|---|---|---|
| almalinux:opensc | 0.23.0-2.el9 · AlmaLinux:9 | Package registry (OSV) |
| debian:opensc | 0.23.0-0.3 · Debian:12 | Package registry (OSV) |
| opensuse:opensc | 0.22.0-150400.3.3.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| red hat:opensc | 0:0.23.0-2.el9 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:opensc-debuginfo | 0:0.23.0-2.el9 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:opensc-debugsource | 0:0.23.0-2.el9 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| suse:opensc | 0.13.0-3.22.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:opensc | 0.22.0-150400.3.3.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.
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 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
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- access.redhat.com/security/cve/CVE-2023-2977
- bugzilla.redhat.com/show_bug.cgi?id=2211088
- github.com/OpenSC/OpenSC/issues/2785
- lists.debian.org/debian-lts-announce/2023/06/msg00025.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FJD4Q4AJSGE5UIJI7OUYZY4HGGCVYQNI/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LAR54OV6EHA56B4XJF6RNPQ4HJ2ITU66/
- lists.debian.org/debian-lts-announce/2024/12/msg00026.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.