# CVE-2018-16427: Memory corruption in n/a

> Attackers with crafted smartcards can cause out-of-bounds reads in OpenSC, leading to application crashes via denial of service.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:P/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-16427, GHSA-35jr-36cj-2w6g, UBUNTU-CVE-2018-16427

## What is CVE-2018-16427?

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

### Official description

Various out of bounds reads when handling responses in OpenSC before 0.19.0-rc1 could be used by attackers able to supply crafted smartcards to potentially crash the opensc library using programs.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2018-16427?

It affects 1 product.


Products: Opensc Project Opensc.

## How do I fix CVE-2018-16427?

Upgrade to a fixed version.

## Is CVE-2018-16427 being exploited?

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

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

## Sources

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

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