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

> Remote attackers can perform man-in-the-middle attacks and spoof servers due to a fixed DSA key in the SSH service.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-w99c-w692-7g63

## What is CVE-2009-4510?

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

### Official description

The SSH service on the TANDBERG Video Communication Server (VCS) before X5.1 uses a fixed DSA key, which makes it easier for remote attackers to conduct man-in-the-middle attacks and spoof arbitrary servers via crafted SSH packets.

Weakness: CWE-310

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

It affects 1 product.


Products: Vsecurity Tandberg Video Communication Server.

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

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

## Is CVE-2009-4510 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4509](https://insights.sbomify.com/CVE-2009-4509/): Auth bypass in n/a (critical 10.0)
- [CVE-2010-1356](https://insights.sbomify.com/CVE-2010-1356/): Other in n/a (critical 10.0)
- [CVE-2010-1355](https://insights.sbomify.com/CVE-2010-1355/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2009-4511](https://insights.sbomify.com/CVE-2009-4511/): Path traversal in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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