dbcve.org
Kh1516i Ip Kvm SwitchHardware / appliance · Aten

CVE-2009-1477

HIGH · 10.0 CVSS v2.0 Published 2009-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The https web interfaces on the ATEN KH1516i IP KVM switch with firmware 1.0.063, the KN9116 IP KVM switch with firmware 1.1.104, and the PN9108 power-control unit have a hardcoded SSL private key, which makes it easier for remote attackers to decrypt https sessions by extracting this key from their own switch and then sniffing network traffic to a switch owned by a different customer.

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 · moderate confidence

ATEN IP KVM switches (KH1516i firmware 1.0.063, KN9116 firmware 1.1.104) and the PN9108 power-control unit contain a hardcoded SSL private key embedded in firmware. Because the same cryptographic key is used across all devices, an attacker who extracts the key from one device can decrypt HTTPS traffic to any other affected device, enabling man-in-the-middle attacks and session hijacking.

MitigationContact ATEN for firmware updates addressing the hardcoded key; if unavailable, implement compensating controls such as VPN tunnels, network segmentation, or internal PKI to isolate and protect these devices. Consider replacing affected hardware if vendor support is unavailable.

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
Kh1516i Ip Kvm SwitchHardware / appliance
Affected:= 1.0.063
Kn9116 Ip Kvm SwitchHardware / appliance
Affected:= 1.1.104
Pn9108 Power Over The NetHardware / appliance
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ATEN KH1516i KVM switches in your environment
    Check your network asset inventory or scan for ATEN KH1516i devices. Access the device web interface or CLI and look for the model identifier in the system information or device status page.
    Affected if A KH1516i device is found with firmware version 1.0.063
  2. Identify ATEN KN9116 KVM switches in your environment
    Check your network asset inventory or scan for ATEN KN9116 devices. Access the device web interface or CLI and look for the model identifier in the system information or device status page.
    Affected if A KN9116 device is found with firmware version 1.1.104
  3. Identify ATEN PN9108 Power Over The Net units in your environment
    Check your network asset inventory or scan for ATEN PN9108 power control units. Access the device web interface or CLI and look for the model identifier in the system information or device status page.
    Affected if A PN9108 device is found at any firmware version
  4. Verify HTTPS management interface is enabled
    On the identified ATEN devices, check the network settings or service configuration to confirm that HTTPS web access or SSL/TLS-based remote management is enabled and accessible.
    Affected if HTTPS management is enabled on any affected device (the hardcoded key vulnerability only applies when SSL/TLS is in use)

You are affected if you have any KH1516i (firmware 1.0.063), KN9116 (firmware 1.1.104), or PN9108 (any version) devices with HTTPS management enabled, because all such devices share the same embedded SSL private key enabling traffic decryption.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Contact ATEN for firmware updates addressing the hardcoded key; if unavailable, implement compensating controls such as VPN tunnels, network segmentation, or internal PKI to isolate and protect these devices. Consider replacing affected hardware if vendor support is unavailable.

Fix this in Kh1516i Ip Kvm Switch Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2009-1477 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2009-1477 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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