# CVE-2010-4523: Memory corruption in n/a

> A physically proximate attacker can execute arbitrary code by presenting a smart card with a long serial number to a system using OpenSC.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 7 Jan 2011
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-4523, GHSA-8q7x-x6wm-6x5q

## What is CVE-2010-4523?

CVE-2010-4523 is a high-severity memory corruption vulnerability in n/a, published on 7 Jan 2011. 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

Multiple stack-based buffer overflows in libopensc in OpenSC 0.11.13 and earlier allow physically proximate attackers to execute arbitrary code via a long serial-number field on a smart card, related to (1) card-acos5.c, (2) card-atrust-acos.c, and (3) card-starcos.c.

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

## Which versions are affected by CVE-2010-4523?

It affects 1 product.


Products: Opensc-Project Opensc.

## How do I fix CVE-2010-4523?

Upgrade to a fixed version.

## Is CVE-2010-4523 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3972](https://insights.sbomify.com/CVE-2008-3972/): Security feature bypass in n/a (medium 6.6)
- [CVE-2008-2235](https://insights.sbomify.com/CVE-2008-2235/): Misconfiguration in n/a (medium 4.9)
- [CVE-2009-0368](https://insights.sbomify.com/CVE-2009-0368/): Security feature bypass in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4523 and fix it if it is affected.

What it is: CVE-2010-4523 is a high-severity memory corruption vulnerability in n/a, published on 7 Jan 2011. 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-2010-4523 in the wild and no public exploit code.

Affected product: n/a. 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-2010-4523/ (Markdown: https://insights.sbomify.com/CVE-2010-4523/index.md)
```

## Sources

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

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