CVE-2024-50370
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 · uneditedA 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 vulnerability can be exploited by remote unauthenticated users capable of interacting with the default "edgserver" service enabled on the access point and malicious commands are executed with root privileges. No authentication is enabled on the service and the source of the vulnerability resides in processing code associated to the "cfg_cmd_set_eth_conf" operation.
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 confidenceCritical OS command injection vulnerability (CWE-78) in Advantech EKI-6333AC wireless access points. The unauthenticated 'edgserver' service fails to sanitize input in the 'cfg_cmd_set_eth_conf' operation, allowing remote attackers to execute arbitrary OS commands with root privileges.
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< 1.6.5< 1.6.5< 1.2.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the EKI-6333AC model variantAccess the device web interface or check the device label to determine if the unit is an EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO variantAffected if The device is any of these three variants and the firmware version is below the patched release
-
Check the installed firmware versionLog into the device web interface and navigate to the Status or System Information page to view the firmware version, or use the command line and run 'cat /proc/version' or check the u-boot environment if accessibleAffected if The firmware version is below 1.6.5 for 2G/2GD models or below 1.2.2 for the 1GPO model
-
Verify the edgserver service is runningAccess the device via SSH or serial console and run 'ps | grep edgserver' to check if the edgserver process is activeAffected if The edgserver process is running on the device
-
Check network exposure of the edgserver serviceReview firewall rules or network configuration to determine if the edgserver service port (typically port 8080 or as configured) is exposed to untrusted networks or the internetAffected if The edgserver service port is accessible from untrusted network segments or directly from the internet
-
Confirm cfg_cmd_set_eth_conf operation is accessibleAttempt to send a specially crafted request to the edgserver endpoint for cfg_cmd_set_eth_conf; in a safe test environment, verify the operation accepts unsanitized input by attempting benign command injection testing with controlled charactersAffected if The cfg_cmd_set_eth_conf operation accepts and processes unsanitized input without validation
The device is affected if it is an EKI-6333AC variant (2G, 2GD, or 1GPO) running firmware below 1.6.5 (or 1.2.2 for 1GPO) and the edgserver service is exposed on the network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.2.21.6.5
Isolate affected devices behind firewalls to block external access to the edgserver service; contact Advantech for firmware updates to patch the vulnerability; disable edgserver if not required for operations.
Firmware 1.6.5+ for EKI-6333AC-2G and EKI-6333AC-2GD; Firmware 1.2.2+ for EKI-6333AC-1GPO
- 1. Identify the exact model number of the Advantech EKI device (EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO)
- 2. Download the firmware update from the official Advantech support portal (support.advantech.com)
- 3. Access the device's web-based management interface or console
- 4. Navigate to the firmware upgrade section
- 5. Upload and apply firmware version 1.6.5 or later for EKI-6333AC-2G/EKI-6333AC-2GD models
- 6. Upload and apply firmware version 1.2.2 or later for EKI-6333AC-1GPO model
- 7. Verify the upgrade was successful by checking the firmware version in the device interface
- 8. Confirm the 'edgserver' service is now running the patched version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50370 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-50370 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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