# CVE-2009-0368: Security feature bypass in n/a

> Physically proximate attackers can bypass PIN requirements to read private data objects from smart cards using low-level commands or debugging tools.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/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:** 2 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-0368, DSA-1734-1, GHSA-q2pp-hq8h-7mm3

## What is CVE-2009-0368?

CVE-2009-0368 is a low-severity vulnerability in n/a, published on 2 Mar 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenSC before 0.11.7 allows physically proximate attackers to bypass intended PIN requirements and read private data objects via a (1) low level APDU command or (2) debugging tool, as demonstrated by reading the 4601 or 4701 file with the opensc-explorer or opensc-tool program.

Weakness: CWE-310

## Which versions are affected by CVE-2009-0368?

It affects 1 product.


Products: Opensc-Project Opensc.

## How do I fix CVE-2009-0368?

Upgrade to a fixed version.

## Is CVE-2009-0368 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0368 exists.

Public exploit code:

- OpenSC 0.11.x - PKCS#11 Implementation Unauthorized Access (exploitdb)

## 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-2008-2235](https://insights.sbomify.com/CVE-2008-2235/): Misconfiguration in n/a (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0368 and fix it if it is affected.

What it is: CVE-2009-0368 is a low-severity vulnerability in n/a, published on 2 Mar 2009. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0368 exists.

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-2009-0368/ (Markdown: https://insights.sbomify.com/CVE-2009-0368/index.md)
```

## Sources

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

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