# CVE-2012-5860: Weak cryptography in n/a

> Attackers can defeat cryptographic protections on Oberthur smart cards due to non-compliant public key generation.

- **Severity:** Medium 4.0 (`AV:L/AC:H/Au:N/C:N/I:C/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c29w-532v-h75c

## What is CVE-2012-5860?

CVE-2012-5860 is a medium-severity vulnerability in n/a, published on 14 Nov 2012. 

### Official description

Unspecified vulnerability on Oberthur ID-One COSMO 5.2, 5.2a, and 64 smart cards makes it easier for attackers to defeat cryptographic protection mechanisms by leveraging the generation of non-compliant public keys.

## Which versions are affected by CVE-2012-5860?

It affects 1 product.


Products: Oberthur Id-One Cosmo.

## How do I fix CVE-2012-5860?

No fix has been published for CVE-2012-5860 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-5860 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5860 and fix it if it is affected.

What it is: CVE-2012-5860 is a medium-severity vulnerability in n/a, published on 14 Nov 2012. 
Exploitation: There is no known exploitation of CVE-2012-5860 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-2012-5860/ (Markdown: https://insights.sbomify.com/CVE-2012-5860/index.md)
```

## Sources

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

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