dbcve.org
Eki 6333ac 2g FirmwareOperating system · Advantech

CVE-2024-50359

HIGH · 7.2 CVSS v3.1 Published 2024-11-26
Fix available
A fix is available. Upgrade to 1.2.2 / 1.6.5 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
A CWE-78 "Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')" was discovered affecting the following devices manufactured by Advantech: EKI-6333AC-2G (<= 1.6.3), EKI-6333AC-2GD (<= v1.6.3) and EKI-6333AC-1GPO (<= v1.2.1). The source of the vulnerability relies on multiple parameters belonging to the "scan_ap" API which are not properly sanitized before being concatenated to OS level commands.

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

OS command injection vulnerability in Advantech EKI-6333AC wireless access points. The scan_ap API endpoint accepts multiple parameters that are directly concatenated to OS-level commands without sanitization, allowing remote attackers to inject arbitrary OS commands.

MitigationVendor firmware update required to patch the vulnerable scan_ap API parameters. Until patch available, restrict network access to device management interface and implement network segmentation as compensating controls.

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 6333ac 2g FirmwareOperating system
Affected:< 1.6.5
Eki 6333ac 2gd FirmwareOperating system
Affected:< 1.6.5
Eki 6333ac 1gpo FirmwareOperating system
Affected:< 1.2.2

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
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 device model
    Access the device web interface or check device label to confirm the exact model variant (EKI-6333AC 2g, 2gd, or 1gpo)
    Affected if Device is any of these three variants
  2. Check firmware version
    Navigate to device web interface System Status or Firmware Upgrade page to view current firmware version. Compare against affected ranges: 2g/2gd versions below 1.6.5, or 1gpo version below 1.2.2
    Affected if Firmware version is lower than the affected threshold for your model
  3. Verify scan_ap API accessibility
    Check if the device management web interface is accessible from network. The vulnerability exists in the scan_ap API endpoint typically found at /cgi-bin/scan_ap or similar path under the web interface
    Affected if Management interface is exposed to untrusted networks without network segmentation or access controls
  4. Review device logs for anomalies
    Check device system logs for unexpected commands, suspicious entries in command history, or signs of injection attempts related to scan_ap functionality
    Affected if Logs show unexpected or injected commands in scan_ap context

You are affected if you have an EKI-6333AC 2g, 2gd, or 1gpo device running firmware below 1.6.5, 1.6.5, or 1.2.2 respectively, and the device management interface is network-accessible.

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 1.2.2 / 1.6.5 or later
Fixed in 1.2.21.6.5
Interim mitigation

Vendor firmware update required to patch the vulnerable scan_ap API parameters. Until patch available, restrict network access to device management interface and implement network segmentation as compensating controls.

Recommended fix Moderate confidence

EKI-6333AC-2G/2GD: firmware 1.6.5; EKI-6333AC-1GPO: firmware 1.2.2

  1. Identify the exact model of your Advantech EKI device (EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO)
  2. Check the current firmware version installed on the device through its admin interface or CLI
  3. Download the appropriate fixed firmware version from the official Advantech support website: version 1.6.5 for EKI-6333AC-2G and EKI-6333AC-2GD, or version 1.2.2 for EKI-6333AC-1GPO
  4. Review Advantech's firmware upgrade documentation for your specific model
  5. Upload and apply the new firmware through the device's web-based management interface or TFTP/CLI method as specified in the documentation
  6. After upgrade, verify the new firmware version is correctly installed
  7. Confirm the 'scan_ap' API function operates normally with the new firmware
Caveat Review upgrade instructions for any model-specific prerequisites or temporary service interruption during the firmware update process

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

Fix this in Eki 6333ac 2g Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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