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

CVE-2024-50365

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 "lan_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 · high confidence

OS command injection vulnerability in Advantech EKI-6333AC wireless access point devices. Multiple parameters in the 'lan_apply' API are not sanitized before being concatenated to OS-level shell commands, allowing authenticated attackers to execute arbitrary OS commands.

MitigationApply vendor firmware updates when available. As an interim measure, restrict network access to the device management interface to trusted IPs only and disable remote management if possible.

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 exact model number (EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO)
    Affected if The device is one of these three models and the firmware version is below the patched version (1.6.5 for 2G/2GD, 1.2.2 for 1GPO)
  2. Check installed firmware version
    Log into the device web interface and navigate to the Status or System Information page to view the firmware version, or use SNMP or the device's CLI to query the firmware version
    Affected if Firmware version is below 1.6.5 for 2G/2GD models or below 1.2.2 for the 1GPO model
  3. Verify lan_apply API accessibility
    Check if the '/lan_apply' endpoint is exposed on the device's web server (typically accessible via HTTP/HTTPS on port 80/443)
    Affected if The API endpoint is reachable over the network and accepts parameters without sanitization checks
  4. Confirm authentication status
    Attempt to access the device management interface to verify whether authentication is required, or check the device security settings for admin account configuration
    Affected if The device allows authenticated access (any valid admin credentials) to the management interface where the vulnerable API resides

The device is affected if it is an Advantech EKI-6333AC model (2G/2GD/1GPO) running firmware below 1.6.5/1.2.2 respectively, and the lan_apply API is accessible with valid admin credentials.

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 when available. As an interim measure, restrict network access to the device management interface to trusted IPs only and disable remote management if possible.

Recommended fix High confidence

EKI-6333AC-2G: upgrade to firmware 1.6.5 | EKI-6333AC-2GD: upgrade to firmware 1.6.5 | EKI-6333AC-1GPO: upgrade to firmware 1.2.2

  1. Obtain the official firmware update from Advantech's support portal or official channels
  2. Locate the specific model firmware: EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO
  3. Download firmware version 1.6.5 for EKI-6333AC-2G and EKI-6333AC-2GD models
  4. Download firmware version 1.2.2 for the EKI-6333AC-1GPO model
  5. Access the device web interface or management console
  6. Navigate to the firmware upgrade or system maintenance section
  7. Upload and apply the appropriate firmware version
  8. Verify the upgrade was successful by checking the firmware version in the device status

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
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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