# CVE-2019-19481: Memory corruption in n/a

> A buffer mishandling flaw in OpenSC allows attackers to cause memory corruption, potentially leading to code execution or denial of service.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 1 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-19481, GHSA-99x7-636q-6hvj, UBUNTU-CVE-2019-19481

## What is CVE-2019-19481?

CVE-2019-19481 is a medium-severity memory corruption vulnerability in Opensc Project Opensc, published on 1 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in OpenSC through 0.19.0 and 0.20.x through 0.20.0-rc3. libopensc/card-cac1.c mishandles buffer limits for CAC certificates.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2019-19481?

It affects 1 product.


Products: Opensc Project Opensc.

## How do I fix CVE-2019-19481?

Upgrade to a fixed version.

## Is CVE-2019-19481 being exploited?

There is no known exploitation of CVE-2019-19481 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-2019-19481 and fix it if it is affected.

What it is: CVE-2019-19481 is a medium-severity memory corruption vulnerability in Opensc Project Opensc, published on 1 Dec 2019. 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-2019-19481 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-2019-19481/ (Markdown: https://insights.sbomify.com/CVE-2019-19481/index.md)
```

## Sources

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

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