CVE-2024-50371
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 "wlan_scan" 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 confidenceA command injection vulnerability exists in the 'wlan_scan' operation of the 'edgserver' service on Advantech EKI-6333AC wireless access points. The service runs with root privileges and has no authentication, allowing remote unauthenticated attackers to inject arbitrary OS commands through unsanitized input in the wlan_scan function.
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 device modelAccess the device's web interface or console and check the model number displayed in the system information or status page. Look for 'EKI-6333AC' variants including 2g, 2gd, or 1gpo.Affected if The device model is Advantech EKI-6333AC 2g, 2gd, or 1gpo.
-
Check firmware versionNavigate to the device's management interface (web UI or CLI) and locate the firmware version information, typically found under System, Status, or About sections. Compare the installed version against the affected ranges.Affected if The firmware version is below 1.6.5 for 2g/2gd models, or below 1.2.2 for 1gpo model.
-
Verify edgserver service is runningAccess the device via SSH or console and run 'ps | grep edgserver' or check the service status to determine if the edgserver process is active.Affected if The edgserver service is running and exposed on the network.
-
Confirm wlan_scan endpoint accessibilityAttempt to access the wlan_scan functionality by sending a request to the edgserver service endpoint (typically via HTTP/HTTPS on the device's management interface). This may require checking exposed APIs or web endpoints.Affected if The wlan_scan operation is accessible without authentication and accepts user-supplied input.
A user is affected if they have an Advantech EKI-6333AC device (2g, 2gd, or 1gpo variant) running firmware below the fixed version with the edgserver service active and the wlan_scan endpoint exposed.
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
Apply vendor firmware updates when available. If no update exists, disable the edgserver service if possible or implement network segmentation to restrict access to the device's management interface.
EKI-6333AC-2G/2GD: firmware >= 1.6.5; EKI-6333AC-1GPO: firmware >= 1.2.2
- 1. Identify the exact model 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 website or contact Advantech directly for the patched firmware
- 3. For EKI-6333AC-2G and EKI-6333AC-2GD: Obtain firmware version 1.6.5 or later
- 4. For EKI-6333AC-1GPO: Obtain firmware version 1.2.2 or later
- 5. Review the device's firmware upgrade documentation for proper installation procedures
- 6. Upload and apply the firmware update via the device's management interface
- 7. After upgrade, verify the edgserver service is functioning correctly and the vulnerability is resolved
- 8. Confirm the device is running the patched firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50371 — 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-50371 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