CVE-2009-1472
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Java client program for ATEN KH1516i and KN9116 IP KVM switches contains a hardcoded AES encryption key embedded in the firmware (versions 1.0.063 and 1.1.104 respectively). An attacker performing man-in-the-middle attacks can use this known key to decrypt session traffic, inject arbitrary Java code into the client, or hijack sessions to gain unauthorized access to machines connected to the KVM switch.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.063= 1.1.104CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the KVM switch modelAccess the KVM switch web interface or console and locate the device information or system status page to confirm the model number is KH1516i or KN9116Affected if The model is KH1516i or KN9116 - other models are not affected by this specific CVE
-
Check the firmware versionIn the KVM switch web interface, go to the Firmware Upgrade or System Information section and record the exact firmware version number displayedAffected if Firmware version is exactly 1.0.063 for KH1516i or exactly 1.1.104 for KN9116 - only these precise versions contain the hardcoded AES key
-
Verify Java client is used for accessCheck if users connect to the KVM switch using the Java-based client application rather than a browser-based or alternative client - the hardcoded key resides in the Java client codeAffected if The Java client program is used to connect to the affected KVM switch - this is the delivery mechanism for the vulnerable code containing the embedded key
-
Inspect network traffic for unencrypted sessionsUse a network sniffer to capture traffic between the Java client and KVM switch during login and session establishment, observing whether encryption is present or if the session traffic could be interceptedAffected if Session traffic is visible or decryptable in transit, indicating the hardcoded key may be in use
-
Review client-side Java code or decompile the client JARLocate the Java client installation files on a client machine, examine the JAR files, or use a Java decompiler to search for AES key constants in the bytecodeAffected if A hardcoded AES key string is found embedded in the Java client code - this confirms the vulnerable client is in use
You are affected if you have an ATEN KH1516i switch running firmware 1.0.063 or a KN9116 switch running firmware 1.1.104, and users connect using the Java client containing the embedded AES key.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace or retire the affected KVM switches if no vendor firmware update is available, as the hardcoded key cannot be changed without a patch. Implement network segmentation and restrict access to the KVM management network to minimize MITM attack surfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1472 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-1472 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data