dbcve.org
Eki 1200 Gateway Series FirmwareOperating system · Advantech

CVE-2014-8385

HIGH · 10.0 CVSS v2.0 Published 2015-02-13
Fix available
A fix is available. Upgrade to after 1.62 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
Buffer overflow on Advantech EKI-1200 gateways with firmware before 1.63 allows remote attackers to execute arbitrary code via unspecified vectors.

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

Buffer overflow vulnerability in Advantech EKI-1200 industrial Ethernet gateways with firmware versions prior to 1.63 allows remote attackers to execute arbitrary code via unspecified vectors. The vulnerability stems from insufficient bounds checking in the firmware, enabling an attacker to overwrite memory and gain code execution.

MitigationUpdate Advantech EKI-1200 gateways to firmware version 1.63 or later to remediate the buffer overflow vulnerability. If immediate patching is not feasible, restrict network access to these devices and monitor for indicators of compromise.

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 1200 Gateway Series FirmwareOperating system
Affected:<= 1.62

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
    Locate the physical device or check network inventory for Advantech EKI-1200 series Ethernet gateways. Confirm the model number matches EKI-1200 or variants (EKI-1221, EKI-1222, etc.).
    Affected if The device is an Advantech EKI-1200 series gateway
  2. Check firmware version via web interface
    Log into the device web interface (if accessible) and navigate to the System Status or About page to view the firmware version number.
    Affected if The firmware version displayed is 1.62 or lower
  3. Check firmware version via CLI
    Access the device console or terminal via Telnet, SSH, or serial connection and run the command to display firmware version (commonly 'show version' or 'sysinfo').
    Affected if The firmware version displayed is 1.62 or lower
  4. Check firmware version via SNMP
    Query the device using SNMP with OID for firmware version (commonly 1.3.6.1.2.1.1.1.0 or vendor-specific OIDs) using snmpwalk or snmpget.
    Affected if The firmware version returned is 1.62 or lower
  5. Compare against affected version range
    If firmware version cannot be directly obtained, check device documentation, management software, or contact vendor to determine the installed firmware version.
    Affected if Confirmed firmware version is 1.62 or below, indicating the device is within the affected range

The environment is affected if any Advantech EKI-1200 gateway is found running firmware version 1.62 or earlier.

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.62
Interim mitigation

Update Advantech EKI-1200 gateways to firmware version 1.63 or later to remediate the buffer overflow vulnerability. If immediate patching is not feasible, restrict network access to these devices and monitor for indicators of compromise.

Recommended fix High confidence

Firmware version 1.63 or later

  1. Obtain the official firmware version 1.63 or later from Advantech's authorized download channels or support portal
  2. Review Advantech's official firmware upgrade documentation for the EKI-1200 series gateways
  3. Follow the vendor's documented firmware update procedure, which typically involves accessing the device's web interface or using their management tools
  4. After upgrading, verify the firmware version has been successfully updated to 1.63 or later
  5. Confirm the device is functioning normally after the upgrade
Caveat Review vendor release notes for any configuration or functionality changes between 1.62 and 1.63 before upgrading

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

Fix this in Eki 1200 Gateway Series Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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