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

CVE-2024-50363

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 "mp_apply" 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 · moderate confidence

OS command injection vulnerability in the mp_apply API of Advantech EKI-6333AC wireless access point series (versions <= 1.6.3 for 2G/2GD models, <= 1.2.1 for 1GPO model). Multiple API parameters are concatenated directly to OS-level commands without sanitization, allowing authenticated attackers to execute arbitrary OS commands.

MitigationApply vendor-supplied firmware updates to patch the command injection vectors; if patches are unavailable, restrict network access to the mp_apply API interface to minimize attack surface.

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
    Check the product label or access the device web interface/system info to confirm whether the unit is an EKI-6333AC 2G, 2GD, or 1GPO model.
    Affected if The device is an Advantech EKI-6333AC series unit (2G, 2GD, or 1GPO variant).
  2. Check firmware version
    Access the device web interface, typically under Administration > Firmware Upgrade or System > Status, to retrieve the currently installed firmware version.
    Affected if Firmware version is below 1.6.5 for 2G/2GD models, or below 1.2.2 for 1GPO model.
  3. Verify mp_apply API accessibility
    Attempt to access the mp_apply API endpoint on the device (commonly via HTTP POST to an endpoint like /cgi-bin/mp_apply or similar). Check if the endpoint responds to requests.
    Affected if The mp_apply API endpoint is reachable on the device and accepts requests.
  4. Confirm authentication status
    Check whether the device requires authentication for API access. Review authentication settings in the device web interface under Security or Access Control settings.
    Affected if The mp_apply API is accessible without requiring valid authentication credentials, or if credentials are required, verify whether the authentication can be bypassed.

A user is affected if they are running an EKI-6333AC 2G/2GD device on firmware < 1.6.5 or 1GPO device on firmware < 1.2.2, with the mp_apply API exposed and accessible (with or without authentication).

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-supplied firmware updates to patch the command injection vectors; if patches are unavailable, restrict network access to the mp_apply API interface to minimize attack surface.

Recommended fix High confidence

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

  1. 1. Download the firmware update from Advantech's official support website for your specific device model (EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO)
  2. 2. Access the device's web-based administrative interface
  3. 3. Navigate to the 'System' or 'Firmware Upgrade' section
  4. 4. Upload the appropriate firmware file (1.6.5 for EKI-6333AC-2G/2GD or 1.2.2 for EKI-6333AC-1GPO)
  5. 5. Initiate the firmware upgrade process and wait for completion
  6. 6. Reboot the device as prompted by the upgrade process
  7. 7. After reboot, verify the firmware version has been updated to the fixed release
Caveat Firmware upgrades may require reconfiguration of wireless settings or other parameters; backup configuration before upgrading

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

Fix this in Eki 6333ac 2g Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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