# CVE-2009-4295: Weak cryptography in n/a

> Remote attackers can decrypt network traffic by predicting shared DSA private keys in Sun Ray DTU firmware, exposing sensitive information.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/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:** No
- **Published:** 11 Dec 2009
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-v37p-x44j-8r75

## What is CVE-2009-4295?

CVE-2009-4295 is a high-severity vulnerability in n/a, published on 11 Dec 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sun Ray Server Software 4.0 and 4.1 does not generate a unique DSA private key for the firmware on each Sun Ray 1, 1g, 100, and 150 DTU device, which makes it easier for remote attackers to obtain sensitive information by predicting a key and then using it to decrypt sniffed network traffic.

Weakness: CWE-310

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

It affects 1 product.


Products: Sun Ray Server Software.

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

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

## Is CVE-2009-4295 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4294](https://insights.sbomify.com/CVE-2009-4294/): Other in n/a (critical 10.0)
- [CVE-2008-2112](https://insights.sbomify.com/CVE-2008-2112/): Privilege escalation in n/a (high 8.5)
- [CVE-2007-6482](https://insights.sbomify.com/CVE-2007-6482/): Denial of service in n/a (high 7.8)
- [CVE-2008-5422](https://insights.sbomify.com/CVE-2008-5422/): Information disclosure in n/a (high 7.5)
- [CVE-2002-2036](https://insights.sbomify.com/CVE-2002-2036/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-4295 is a high-severity vulnerability in n/a, published on 11 Dec 2009. 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-2009-4295 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-2009-4295/ (Markdown: https://insights.sbomify.com/CVE-2009-4295/index.md)
```

## Sources

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

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