dbcve.org
Eki 1321 Series FirmwareOperating system · Advantech

CVE-2015-6476

HIGH · 10.0 CVSS v2.0 Published 2015-11-07
Fix available
A fix is available. Upgrade to after 1.96 or later.
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
Advantech EKI-122x-BE devices with firmware before 1.65, EKI-132x devices with firmware before 1.98, and EKI-136x devices with firmware before 1.27 have hardcoded SSH keys, which makes it easier for remote attackers to obtain access via an SSH 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 confidence

Advantech EKI-122x-BE, EKI-132x, and EKI-136x devices contain hardcoded SSH keys embedded in firmware versions before 1.65, 1.98, and 1.27 respectively. This backdoor allows remote attackers to authenticate via SSH without knowing legitimate credentials, achieving full remote access to the device.

MitigationUpgrade firmware to version 1.65 (EKI-122x-BE), 1.98 (EKI-132x), or 1.27 (EKI-136x) or later. If firmware cannot be updated, disable SSH access entirely and restrict network access to these devices via firewall rules or network segmentation.

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
Eki 1321 Series FirmwareOperating system
Affected:<= 1.96
Eki 1322 Series FirmwareOperating system
Affected:<= 1.96
Eki 1361 Series FirmwareOperating system
Affected:<= 1.17
Eki 1362 Series FirmwareOperating system
Affected:<= 1.17
Eki 122x Series FirmwareOperating system
Affected:<= 1.49

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 the device model
    Access the device's web interface or console and locate the model number. Look for EKI-122x-BE, EKI-1321, EKI-1322, EKI-1361, or EKI-1362 in the system information or device label.
    Affected if The device model is any of EKI-122x-BE, EKI-1321, EKI-1322, EKI-1361, or EKI-1362.
  2. Check the firmware version
    In the device's web interface, navigate to the System or Status page to view the firmware version. Alternatively, access the device via console and run the appropriate command to display firmware version (commonly 'version' or 'show version').
    Affected if The firmware version is at or below 1.49 for EKI-122x-BE, at or below 1.96 for EKI-1321/EKI-1322, or at or below 1.17 for EKI-1361/EKI-1362.
  3. Confirm SSH service is enabled
    Check the device configuration via web interface under Network or Services settings to verify if SSH is enabled. From the console, run 'show services' or similar command to list enabled services.
    Affected if SSH service is enabled on the device.
  4. Verify SSH is network accessible
    From an external host, attempt a TCP connection to port 22 (or the configured SSH port) toward the device IP address using 'nc -zv <device_ip> 22' or nmap to confirm the SSH port is open and reachable.
    Affected if Port 22 (or configured SSH port) is open and reachable from a network location where attackers could connect.

A user is affected if they have an EKI-122x-BE, EKI-1321, EKI-1322, EKI-1361, or EKI-1362 device running firmware at or below the affected version (1.49, 1.96, or 1.17 respectively) with SSH enabled and accessible from the network.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.96
Interim mitigation

Upgrade firmware to version 1.65 (EKI-122x-BE), 1.98 (EKI-132x), or 1.27 (EKI-136x) or later. If firmware cannot be updated, disable SSH access entirely and restrict network access to these devices via firewall rules or network segmentation.

Recommended fix High confidence

EKI-122x: firmware >= 1.65 | EKI-132x: firmware >= 1.98 | EKI-136x: firmware >= 1.27

  1. 1. Identify the exact model number (EKI-122x, EKI-1321, EKI-1322, EKI-1361, or EKI-1362) of the Advantech device.
  2. 2. Download the firmware update from the official Advantech support website (advantech.com) or contact Advantech technical support.
  3. 3. For EKI-122x series devices: upgrade to firmware version 1.65 or later.
  4. 4. For EKI-1321/1322 series devices: upgrade to firmware version 1.98 or later.
  5. 5. For EKI-1361/1362 series devices: upgrade to firmware version 1.27 or later.
  6. 6. Follow the vendor's firmware upgrade procedure, which typically involves accessing the device's web interface or using a dedicated firmware update tool.
  7. 7. After upgrading, verify that the SSH service is using new, unique keys and not the hardcoded keys.
  8. 8. As a secondary precaution, if SSH is not required for operations, consider disabling the SSH service via the device configuration.
Caveat Review release notes for any changes to device configuration or behavior before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Eki 1321 Series Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6476 — 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-2015-6476 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