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

CVE-2024-50364

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 "export_log" 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 point devices (versions <=1.6.3 for 2G/2GD models, <=1.2.1 for 1GPO model). Multiple parameters in the 'export_log' API are not sanitized before being concatenated into OS-level commands, allowing authenticated attackers to execute arbitrary OS commands.

MitigationUpdate device firmware to versions containing the security patch. If firmware updates are unavailable, implement network segmentation and restrict access to the device's management interface to trusted personnel only.

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 the device label to confirm the model is Advantech EKI-6333AC (2G, 2GD, or 1GPO variant)
    Affected if Device is not an EKI-6333AC variant
  2. Determine firmware version
    Log into the device management interface and navigate to the firmware or system information page to find the installed firmware version number
    Affected if Firmware version is 1.6.3 or lower for 2G/2GD models, or 1.2.1 or lower for 1GPO model
  3. Verify the export_log API endpoint
    Attempt to access the /export_log API endpoint on the device (typically via HTTP GET or POST request to the device IP)
    Affected if The export_log API is reachable and responds to requests
  4. Confirm authentication status
    Check whether the device requires authentication for administrative access and whether valid credentials are configured
    Affected if The device management interface is accessible without authentication or uses default credentials

A device is affected if it is an EKI-6333AC (2G/2GD or 1GPO model) running firmware below 1.6.5 (for 2G/2GD) or below 1.2.2 (for 1GPO) and the export_log API is accessible to an authenticated attacker.

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

Update device firmware to versions containing the security patch. If firmware updates are unavailable, implement network segmentation and restrict access to the device's management interface to trusted personnel only.

Recommended fix High confidence

Upgrade to EKI-6333AC-2G/2GD firmware 1.6.5 or EKI-6333AC-1GPO firmware 1.2.2

  1. 1. Identify the exact model number of the affected Advantech EKI device (EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO)
  2. 2. Navigate to Advantech's official support portal or website to locate the firmware download section
  3. 3. Download the appropriate firmware version: version 1.6.5 for EKI-6333AC-2G and EKI-6333AC-2GD, or version 1.2.2 for EKI-6333AC-1GPO
  4. 4. Review the firmware upgrade instructions provided by Advantech
  5. 5. Backup the current device configuration before performing the upgrade
  6. 6. Follow the vendor's recommended firmware update procedure to apply the new firmware version
  7. 7. After upgrade, verify the device is functioning normally and the firmware version reflects the patched release
Caveat Review vendor release notes for any changes in functionality or configuration requirements between versions

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

Fix this in Eki 6333ac 2g 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-2024-50364 — 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-50364 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