# CVE-2006-0898: Weak cryptography in n/a

> Weak encryption in Perl Crypt::CBC module allows attackers to potentially decrypt data when using ciphers with block sizes larger than 8 bytes.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-0898, DSA-996-1, GHSA-qpjg-v8f6-cw7j

## What is CVE-2006-0898?

CVE-2006-0898 is a low-severity vulnerability in n/a, published on 25 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Crypt::CBC Perl module 2.16 and earlier, when running in RandomIV mode, uses an initialization vector (IV) of 8 bytes, which results in weaker encryption when used with a cipher that requires a larger block size than 8 bytes, such as Rijndael.

## Which versions are affected by CVE-2006-0898?

It affects 1 product.


Products: Lincoln D. Stein Crypt Cbc.

## How do I fix CVE-2006-0898?

Upgrade to a fixed version.

## Is CVE-2006-0898 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0898 and fix it if it is affected.

What it is: CVE-2006-0898 is a low-severity vulnerability in n/a, published on 25 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0898 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-2006-0898/ (Markdown: https://insights.sbomify.com/CVE-2006-0898/index.md)
```

## Sources

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

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