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

> Attackers can exploit uninitialized memory in OpenSC via crafted smart card responses, potentially leading to code execution or crashes.

- **Severity:** Low 3.9 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2024
- **Updated:** 30 Jun 2026
- **Also known as:** AZL-48721, AZL-48768, BELL-CVE-2024-45616, DEBIAN-CVE-2024-45616, GHSA-2mjg-798r-mxwh, UBUNTU-CVE-2024-45616

## What is CVE-2024-45616?

CVE-2024-45616 is a low-severity memory corruption vulnerability in Opensc Project Opensc, published on 3 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-908 (Use of Uninitialized Resource), CWE-457 (Use of Uninitialized Variable)

## Which versions are affected by CVE-2024-45616?

It affects 2 products.


Products: Opensc Project Opensc, Redhat Enterprise Linux.

## How do I fix CVE-2024-45616?

Apply the vendor's patch.

## Is CVE-2024-45616 being exploited?

There is no known exploitation of CVE-2024-45616 in the wild and no public exploit code.

## Other vulnerabilities in Opensc Project Opensc

- [CVE-2021-34193](https://insights.sbomify.com/CVE-2021-34193/): Memory corruption in n/a (high 7.5)
- [CVE-2019-16058](https://insights.sbomify.com/CVE-2019-16058/): Memory corruption in n/a (high 7.5)
- [CVE-2019-6502](https://insights.sbomify.com/CVE-2019-6502/): Denial of service in n/a (high 7.5)
- [CVE-2023-2977](https://insights.sbomify.com/CVE-2023-2977/): Memory corruption in OpenSC (high 7.1)
- [CVE-2019-20792](https://insights.sbomify.com/CVE-2019-20792/): Use after free in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45616 and fix it if it is affected.

What it is: CVE-2024-45616 is a low-severity memory corruption vulnerability in Opensc Project Opensc, published on 3 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45616 in the wild and no public exploit code.

Affected product: Opensc Project Opensc. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-45616/ (Markdown: https://insights.sbomify.com/CVE-2024-45616/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45616
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45616
- OSV: https://osv.dev/vulnerability/CVE-2024-45616

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-45616/
Summaries are generated and may contain mistakes; the official description above is the record.
