# CVE-2001-0856: Weak cryptography in n/a

> An attacker with physical access and specific permissions can brute-force DES/3DES keys from the IBM 4758 cryptographic coprocessor.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hp82-2c75-2m8m

## What is CVE-2001-0856?

CVE-2001-0856 is a medium-severity vulnerability in n/a, published on 22 Nov 2001. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Common Cryptographic Architecture (CCA) in IBM 4758 allows an attacker with physical access to the system and Combine_Key_Parts permissions, to steal DES and 3DES keys by using a brute force attack to create a 3DES exporter key.

## Which versions are affected by CVE-2001-0856?

It affects 1 product.


Products: Ibm 4758.

## How do I fix CVE-2001-0856?

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

## Is CVE-2001-0856 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0856 and fix it if it is affected.

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

## Sources

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

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