CVE-2009-1473
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 (1) Windows and (2) Java client programs for the ATEN KH1516i IP KVM switch with firmware 1.0.063 and the KN9116 IP KVM switch with firmware 1.1.104 do not properly use RSA cryptography for a symmetric session-key negotiation, which makes it easier for remote attackers to (a) decrypt network traffic, or (b) conduct man-in-the-middle attacks, by repeating unspecified "client-side calculations."
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 Windows and Java client programs for ATEN KH1516i IP KVM (firmware 1.0.063) and KN9116 IP KVM (firmware 1.1.104) switches use improper RSA cryptography during symmetric session-key negotiation, allowing remote attackers to decrypt network traffic or perform man-in-the-middle attacks by replaying client-side calculation values.
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 ATEN KVM device modelAccess the KVM switch administrative interface or check device documentation/labels to confirm the exact model is KH1516i or KN9116Affected if The device model is ATEN KH1516i or KN9116
-
Check KVM switch firmware versionLog into the KVM switch web interface or use the administrative console to view the firmware version informationAffected if Firmware version equals 1.0.063 for KH1516i or 1.1.104 for KN9116
-
Verify Java or Windows client versionCheck installed client program version through program properties or about menu in the ATEN KVM client softwareAffected if Client version corresponds to the affected firmware versions (1.0.063 or 1.1.104)
-
Confirm network accessibility of KVM switchVerify the KVM switch is reachable over the network and accepts remote connectionsAffected if The KVM switch is accessible remotely and uses the affected firmware version
The environment is affected if an ATEN KH1516i or KN9116 IP KVM switch with firmware version 1.0.063 or 1.1.104 respectively is in use and accessible over the network.
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 dataUpdate the device firmware and client software to patched versions if available from ATEN; if no patch exists, isolate the KVM switches behind a VPN or restricted network segment and monitor for unauthorized access attempts.
- Consultation6.0 h
- Implementation4.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 $4,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1473 — 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-1473 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