# CVE-2008-2235: Misconfiguration in n/a

> Weak file permissions in OpenSC allow physically proximate attackers to change PINs on Siemens CardOS M4 smart cards and USB tokens.

- **Severity:** Medium 4.9 (`AV:L/AC:L/Au:N/C:N/I:C/A:N`)
- **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 Aug 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-2235, GHSA-8cph-r8x9-fxx9

## What is CVE-2008-2235?

CVE-2008-2235 is a medium-severity vulnerability in n/a, published on 1 Aug 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenSC before 0.11.5 uses weak permissions (ADMIN file control information of 00) for the 5015 directory on smart cards and USB crypto tokens running Siemens CardOS M4, which allows physically proximate attackers to change the PIN.

Weakness: CWE-310

## Which versions are affected by CVE-2008-2235?

It affects 1 product.


Products: Opensc-Project Opensc.

## How do I fix CVE-2008-2235?

Upgrade to a fixed version.

## Is CVE-2008-2235 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4523](https://insights.sbomify.com/CVE-2010-4523/): Memory corruption in n/a (high 7.2)
- [CVE-2008-3972](https://insights.sbomify.com/CVE-2008-3972/): Security feature bypass in n/a (medium 6.6)
- [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-2008-2235 and fix it if it is affected.

What it is: CVE-2008-2235 is a medium-severity vulnerability in n/a, published on 1 Aug 2008. 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-2008-2235 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-2008-2235/ (Markdown: https://insights.sbomify.com/CVE-2008-2235/index.md)
```

## Sources

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

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