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

CVE-2024-50367

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 "sta_log_htm" 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-6333 series wireless access points. The 'sta_log_htm' API endpoint contains multiple parameters that are not properly sanitized before being passed to OS-level command execution, allowing authenticated attackers to inject arbitrary OS commands.

MitigationApply vendor firmware updates to address the command injection vectors in the sta_log_htm API. If no patch is available, implement network segmentation and restrict administrative access 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 the device model
    Access the device web interface or SSH console and locate the model number under System Status, Device Info, or similar administration page. Confirm the model is EKI-6333ac 2g, EKI-6333ac 2gd, or EKI-6333ac 1gpo.
    Affected if The device model is one of the three affected EKI-6333 variants.
  2. Determine the installed firmware version
    In the device web interface, navigate to the Firmware Upgrade, System Maintenance, or About section to view the current firmware version. Alternatively, access the device via SSH or console and run commands such as 'cat /proc/version', 'version', or check for a firmware info file if available.
    Affected if The firmware version cannot be confirmed as 1.6.5 or higher for EKI-6333ac 2g/2gd, or 1.2.2 or higher for EKI-6333ac 1gpo.
  3. Compare firmware version to affected ranges
    Review the firmware version identified in step 2 against the affected version thresholds: EKI-6333ac 2g < 1.6.5, EKI-6333ac 2gd < 1.6.5, EKI-6333ac 1gpo < 1.2.2.
    Affected if The installed firmware version is below the specified threshold for the detected model.
  4. Verify administrative interface exposure
    Check the device network configuration to determine if the web management interface (HTTP/HTTPS) or SSH is accessible from untrusted network segments or the internet. Review firewall rules, NAT configurations, or port forwarding settings on upstream devices.
    Affected if The administrative interface is reachable from untrusted networks, allowing authenticated attackers to reach the vulnerable endpoint.
  5. Assess authentication token or session handling
    If you have access to the device, inspect the authentication mechanism for the sta_log_htm API endpoint. Determine whether session tokens are properly validated or if authentication can be bypassed in certain conditions.
    Affected if The sta_log_htm endpoint accepts commands without proper authentication validation or with weak session handling.

The environment is affected if the device is an EKI-6333ac 2g, 2gd, or 1gpo model running firmware below 1.6.5, 1.6.5, or 1.2.2 respectively, and the administrative interface is accessible to potential attackers.

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

Apply vendor firmware updates to address the command injection vectors in the sta_log_htm API. If no patch is available, implement network segmentation and restrict administrative access to trusted personnel only.

Recommended fix High confidence

EKI-6333AC-2G: firmware >= 1.6.5 | EKI-6333AC-2GD: firmware >= 1.6.5 | EKI-6333AC-1GPO: firmware >= 1.2.2

  1. 1. Obtain the official firmware update from Advantech's support portal or official channels for your specific device model (EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO).
  2. 2. Access the device's web-based management interface or administrative console using authorized credentials.
  3. 3. Navigate to the firmware update or system maintenance section of the management interface.
  4. 4. Upload the appropriate firmware version: version 1.6.5 or later for EKI-6333AC-2G and EKI-6333AC-2GD; version 1.2.2 or later for EKI-6333AC-1GPO.
  5. 5. Confirm the firmware upload and allow the device to complete the update process without interrupting power.
  6. 6. After the device restarts, verify that the new firmware version is installed and that the device is functioning normally.
  7. 7. If available, review the device configuration to ensure previous settings are preserved or reapply as needed.

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

Fix this in Eki 6333ac 2g Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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