OESA-2024-2245 (CVE-2024-45615)
Vulnerability from osv_openeuler – Published: 2024-10-12 11:07 – Updated: 2026-08-06 11:07 – Source websiteOpenSC provides a set of libraries and utilities to work with smart cards. Its main focus is on cards that support cryptographic operations, and facilitate their use in security applications such as authentication, mail encryption and digital signatures. OpenSC implements the standard APIs to smart cards, e.g. PKCS#11 API, Windows’ Smart Card Minidriver and macOS Tokend.
Security Fix(es):
A vulnerability was found in OpenSC, OpenSC tools, PKCS#11 module, minidriver, and CTK. The problem is missing initialization of variables expected to be initialized (as arguments to other functions, etc.).(CVE-2024-45615)
A vulnerability was found in OpenSC, OpenSC tools, PKCS#11 module, minidriver, and CTK. An attacker could use a crafted USB Device or Smart Card, which would present the system with a specially crafted response to APDUs.
The following problems were caused by insufficient control of the response APDU buffer and its length when communicating with the card.(CVE-2024-45616)
A vulnerability was found in OpenSC, OpenSC tools, PKCS#11 module, minidriver, and CTK. An attacker could use a crafted USB Device or Smart Card, which would present the system with a specially crafted response to APDUs.
Insufficient or missing checking of return values of functions leads to unexpected work with variables that have not been initialized.(CVE-2024-45617)
A vulnerability was found in pkcs15-init in OpenSC. An attacker could use a crafted USB Device or Smart Card, which would present the system with a specially crafted response to APDUs.
Insufficient or missing checking of return values of functions leads to unexpected work with variables that have not been initialized.(CVE-2024-45618)
A vulnerability was found in OpenSC, OpenSC tools, PKCS#11 module, minidriver, and CTK. An attacker could use a crafted USB Device or Smart Card, which would present the system with a specially crafted response to APDUs. When buffers are partially filled with data, initialized parts of the buffer can be incorrectly accessed.(CVE-2024-45619)
A vulnerability was found in the pkcs15-init tool in OpenSC. An attacker could use a crafted USB Device or Smart Card, which would present the system with a specially crafted response to APDUs. When buffers are partially filled with data, initialized parts of the buffer can be incorrectly accessed.(CVE-2024-45620)
A heap-based buffer overflow vulnerability was found in the libopensc OpenPGP driver. A crafted USB device or smart card with malicious responses to the APDUs during the card enrollment process using the pkcs15-init tool may lead to out-of-bound rights, possibly resulting in arbitrary code execution.(CVE-2024-8443)
| Ecosystem | Package | Version |
|---|---|---|
| openEuler:22.03-LTS-SP1 |
opensc
pkg:rpm/openEuler/opensc&distro=openEuler-22.03-LTS-SP1
|
Affected: < 0.21.0-11.oe2203sp1 (ecosystem)
|
| openEuler:24.03-LTS |
opensc
pkg:rpm/openEuler/opensc&distro=openEuler-24.03-LTS
|
Affected: < 0.23.0-7.oe2403 (ecosystem)
|
| openEuler:22.03-LTS-SP4 |
opensc
pkg:rpm/openEuler/opensc&distro=openEuler-22.03-LTS-SP4
|
Affected: < 0.21.0-11.oe2203sp4 (ecosystem)
|
| openEuler:22.03-LTS-SP3 |
opensc
pkg:rpm/openEuler/opensc&distro=openEuler-22.03-LTS-SP3
|
Affected: < 0.21.0-11.oe2203sp3 (ecosystem)
|
| openEuler:20.03-LTS-SP4 |
opensc
pkg:rpm/openEuler/opensc&distro=openEuler-20.03-LTS-SP4
|
Affected: < 0.20.0-15.oe2003sp4 (ecosystem)
|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"opensc-0.21.0-11.oe2203sp1.aarch64.rpm",
"opensc-debuginfo-0.21.0-11.oe2203sp1.aarch64.rpm",
"opensc-debugsource-0.21.0-11.oe2203sp1.aarch64.rpm"
],
"noarch": [
"opensc-help-0.21.0-11.oe2203sp1.noarch.rpm"
],
"src": [
"opensc-0.21.0-11.oe2203sp1.src.rpm"
],
"x86_64": [
"opensc-0.21.0-11.oe2203sp1.x86_64.rpm",
"opensc-debuginfo-0.21.0-11.oe2203sp1.x86_64.rpm",
"opensc-debugsource-0.21.0-11.oe2203sp1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP1",
"name": "opensc",
"purl": "pkg:rpm/openEuler/opensc\u0026distro=openEuler-22.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.21.0-11.oe2203sp1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"opensc-0.23.0-7.oe2403.aarch64.rpm",
"opensc-debuginfo-0.23.0-7.oe2403.aarch64.rpm",
"opensc-debugsource-0.23.0-7.oe2403.aarch64.rpm",
"opensc-help-0.23.0-7.oe2403.aarch64.rpm"
],
"src": [
"opensc-0.23.0-7.oe2403.src.rpm"
],
"x86_64": [
"opensc-0.23.0-7.oe2403.x86_64.rpm",
"opensc-debuginfo-0.23.0-7.oe2403.x86_64.rpm",
"opensc-debugsource-0.23.0-7.oe2403.x86_64.rpm",
"opensc-help-0.23.0-7.oe2403.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS",
"name": "opensc",
"purl": "pkg:rpm/openEuler/opensc\u0026distro=openEuler-24.03-LTS"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.23.0-7.oe2403"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"opensc-0.21.0-11.oe2203sp4.aarch64.rpm",
"opensc-debuginfo-0.21.0-11.oe2203sp4.aarch64.rpm",
"opensc-debugsource-0.21.0-11.oe2203sp4.aarch64.rpm"
],
"noarch": [
"opensc-help-0.21.0-11.oe2203sp4.noarch.rpm"
],
"src": [
"opensc-0.21.0-11.oe2203sp4.src.rpm"
],
"x86_64": [
"opensc-0.21.0-11.oe2203sp4.x86_64.rpm",
"opensc-debuginfo-0.21.0-11.oe2203sp4.x86_64.rpm",
"opensc-debugsource-0.21.0-11.oe2203sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP4",
"name": "opensc",
"purl": "pkg:rpm/openEuler/opensc\u0026distro=openEuler-22.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.21.0-11.oe2203sp4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"opensc-0.21.0-11.oe2203sp3.aarch64.rpm",
"opensc-debuginfo-0.21.0-11.oe2203sp3.aarch64.rpm",
"opensc-debugsource-0.21.0-11.oe2203sp3.aarch64.rpm"
],
"noarch": [
"opensc-help-0.21.0-11.oe2203sp3.noarch.rpm"
],
"src": [
"opensc-0.21.0-11.oe2203sp3.src.rpm"
],
"x86_64": [
"opensc-0.21.0-11.oe2203sp3.x86_64.rpm",
"opensc-debuginfo-0.21.0-11.oe2203sp3.x86_64.rpm",
"opensc-debugsource-0.21.0-11.oe2203sp3.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP3",
"name": "opensc",
"purl": "pkg:rpm/openEuler/opensc\u0026distro=openEuler-22.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.21.0-11.oe2203sp3"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"opensc-0.20.0-15.oe2003sp4.aarch64.rpm",
"opensc-debuginfo-0.20.0-15.oe2003sp4.aarch64.rpm",
"opensc-debugsource-0.20.0-15.oe2003sp4.aarch64.rpm"
],
"noarch": [
"opensc-help-0.20.0-15.oe2003sp4.noarch.rpm"
],
"src": [
"opensc-0.20.0-15.oe2003sp4.src.rpm"
],
"x86_64": [
"opensc-0.20.0-15.oe2003sp4.x86_64.rpm",
"opensc-debuginfo-0.20.0-15.oe2003sp4.x86_64.rpm",
"opensc-debugsource-0.20.0-15.oe2003sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP4",
"name": "opensc",
"purl": "pkg:rpm/openEuler/opensc\u0026distro=openEuler-20.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.20.0-15.oe2003sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Low"
},
"details": "OpenSC provides a set of libraries and utilities to work with smart cards. Its main focus is on cards that support cryptographic operations, and facilitate their use in security applications such as authentication, mail encryption and digital signatures. OpenSC implements the standard APIs to smart cards, e.g. PKCS#11 API, Windows\u2019 Smart Card Minidriver and macOS Tokend.\r\n\r\nSecurity Fix(es):\r\n\r\nA vulnerability was found in OpenSC, OpenSC tools, PKCS#11 module, minidriver, and CTK. \nThe problem is missing initialization of variables expected to be initialized (as arguments to other functions, etc.).(CVE-2024-45615)\r\n\r\nA vulnerability was found in OpenSC, OpenSC tools, PKCS#11 module, minidriver, and CTK. An attacker could use a crafted USB Device or Smart Card, which would present the system with a specially crafted response to APDUs. \r\n\r\nThe following problems were caused by insufficient control of the response APDU buffer and its length when communicating with the card.(CVE-2024-45616)\r\n\r\nA vulnerability was found in OpenSC, OpenSC tools, PKCS#11 module, minidriver, and CTK. An attacker could use a crafted USB Device or Smart Card, which would present the system with a specially crafted response to APDUs. \r\n\r\nInsufficient or missing checking of return values of functions leads to unexpected work with variables that have not been initialized.(CVE-2024-45617)\r\n\r\nA vulnerability was found in pkcs15-init in OpenSC. An attacker could use a crafted USB Device or Smart Card, which would present the system with a specially crafted response to APDUs. \r\n\r\nInsufficient or missing checking of return values of functions leads to unexpected work with variables that have not been initialized.(CVE-2024-45618)\r\n\r\nA vulnerability was found in OpenSC, OpenSC tools, PKCS#11 module, minidriver, and CTK. An attacker could use a crafted USB Device or Smart Card, which would present the system with a specially crafted response to APDUs. When buffers are partially filled with data, initialized parts of the buffer can be incorrectly accessed.(CVE-2024-45619)\r\n\r\nA vulnerability was found in the pkcs15-init tool in OpenSC. An attacker could use a crafted USB Device or Smart Card, which would present the system with a specially crafted response to APDUs. When buffers are partially filled with data, initialized parts of the buffer can be incorrectly accessed.(CVE-2024-45620)\r\n\r\nA heap-based buffer overflow vulnerability was found in the libopensc OpenPGP driver. A crafted USB device or smart card with malicious responses to the APDUs during the card enrollment process using the `pkcs15-init` tool may lead to out-of-bound rights, possibly resulting in arbitrary code execution.(CVE-2024-8443)",
"id": "OESA-2024-2245",
"modified": "2026-08-06T11:07:43Z",
"published": "2024-10-12T11:07:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2245"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45615"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45616"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45617"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45618"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45619"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45620"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-8443"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "opensc security update",
"upstream": [
"CVE-2024-45615",
"CVE-2024-45616",
"CVE-2024-45617",
"CVE-2024-45618",
"CVE-2024-45619",
"CVE-2024-45620",
"CVE-2024-8443"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.