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

> Remote attackers can decrypt communications and conduct man-in-the-middle attacks due to a shared private DSA key across installations.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wxfq-3983-gh23

## What is CVE-2006-0231?

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

### Official description

Symantec Scan Engine 5.0.0.24, and possibly other versions before 5.1.0.7, uses the same private DSA key for each installation, which allows remote attackers to conduct man-in-the-middle attacks and decrypt communications.

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

It affects 1 product.


Products: Symantec Antivirus Scan Engine.

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

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

## Is CVE-2006-0231 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0230](https://insights.sbomify.com/CVE-2006-0230/): Auth bypass in n/a (critical 10.0)
- [CVE-2005-2758](https://insights.sbomify.com/CVE-2005-2758/): Integer overflow in n/a (critical 10.0)
- [CVE-2007-0447](https://insights.sbomify.com/CVE-2007-0447/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-3699](https://insights.sbomify.com/CVE-2007-3699/): Denial of service in n/a (critical 9.3)
- [CVE-2005-0249](https://insights.sbomify.com/CVE-2005-0249/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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