# CVE-2024-1454: Opensc: memory use after free in authentic driver when updating token info

> A use-after-free in OpenSC's AuthentIC driver allows attackers with physical access and a crafted smart card to compromise card management operations.

- **Severity:** Low 3.4 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Feb 2024
- **Updated:** 7 Nov 2025
- **Also known as:** AZL-34384, AZL-35078, BELL-CVE-2024-1454, DEBIAN-CVE-2024-1454, GHSA-6q4q-mhg5-v6xh, openSUSE-SU-2024:13733-1

## What is CVE-2024-1454?

CVE-2024-1454 is a low-severity use after free vulnerability in Fedoraproject Fedora, published on 12 Feb 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The use-after-free vulnerability was found in the AuthentIC driver in OpenSC packages, occuring in the card enrolment process using pkcs15-init when a user or administrator enrols or modifies cards. An attacker must have physical access to the computer system and requires a crafted USB device or smart card to present the system with specially crafted responses to the APDUs, which are considered high complexity and low severity. This manipulation can allow for compromised card management operations during enrolment.

Weakness: CWE-416 (Use After Free)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `opensc` | openSUSE:Tumbleweed | All versions | 0.24.0-2.1 |

Products: Fedoraproject Fedora, Opensc Project Opensc, Redhat Enterprise Linux.

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

Apply the vendor's patch.

## Is CVE-2024-1454 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1454 is a low-severity use after free vulnerability in Fedoraproject Fedora, published on 12 Feb 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-1454 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-1454/ (Markdown: https://insights.sbomify.com/CVE-2024-1454/index.md)
```

## Sources

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

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