# CVE-2009-1472: Hardcoded credentials in n/a

> Hardcoded AES key in ATEN IP KVM Java client allows man-in-the-middle attackers to execute code or access connected machines.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8rxj-jcx7-7vqh

## What is CVE-2009-1472?

CVE-2009-1472 is a critical vulnerability in n/a, published on 27 May 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Java client program for the ATEN KH1516i IP KVM switch with firmware 1.0.063 and the KN9116 IP KVM switch with firmware 1.1.104 has a hardcoded AES encryption key, which makes it easier for man-in-the-middle attackers to (1) execute arbitrary Java code, or (2) gain access to machines connected to the switch, by hijacking a session.

Weakness: CWE-310

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

It affects 2 products.


Products: Aten Kh1516i Ip Kvm Switch, Aten Kn9116 Ip Kvm Switch.

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

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

## Is CVE-2009-1472 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1473](https://insights.sbomify.com/CVE-2009-1473/): Weak cryptography in n/a (critical 10.0)
- [CVE-2009-1477](https://insights.sbomify.com/CVE-2009-1477/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2009-1474](https://insights.sbomify.com/CVE-2009-1474/): Weak cryptography in n/a (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1472 is a critical vulnerability in n/a, published on 27 May 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-1472 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-1472/ (Markdown: https://insights.sbomify.com/CVE-2009-1472/index.md)
```

## Sources

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

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