CVE-2024-50372
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 "backup_config_to_utility" 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 critical OS command injection vulnerability (CWE-78) exists in Advantech EKI-6333AC wireless access point devices (models 2G, 2GD, and 1GPO). The flaw resides in the 'backup_config_to_utility' operation processed by the default 'edgserver' service, which runs without authentication and allows remote unauthenticated 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 variantLocate the model label on the device physical label or check the device web interface/system status page for the exact model designation (2G, 2GD, or 1GPO)Affected if The model is EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO
-
Determine the installed firmware versionAccess the device administration interface and navigate to System > Firmware Upgrade or System > Status to view the current firmware version. Alternatively, check via CLI if accessible.Affected if The firmware version is below 1.6.5 for 2G/2GD models, or below 1.2.2 for 1GPO model
-
Verify if the edgserver service is runningCheck the device running processes via CLI (if accessible) or review the device administration interface for active services. The vulnerable service is named 'edgserver'.Affected if The edgserver service is enabled and running on the device
-
Assess network exposure of the edgserver serviceReview firewall rules, port scans, or network access control lists to determine if port/service used by edgserver (typically HTTP/HTTPS on ports 80/443 or custom ports) is exposed to untrusted networks or the internet.Affected if The edgserver service port is accessible from untrusted network segments or the public internet
If the device is an affected model variant, runs a firmware version below the safe thresholds, and has the edgserver service exposed to network attackers, the environment is vulnerable to remote command injection.
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
Upgrade firmware to versions above 1.6.3 (for EKI-6333AC-2G/2GD) or above v1.2.1 (for EKI-6333AC-1GPO). If patches unavailable, disable the edgserver service via device administration and apply network segmentation to isolate affected devices.
EKI-6333AC-2G and EKI-6333AC-2GD: upgrade to firmware 1.6.5 or later; EKI-6333AC-1GPO: upgrade to firmware 1.2.2 or later
- 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 portal (advantech.com)
- 3. Review the firmware upgrade instructions in the device documentation
- 4. Upload and apply firmware version 1.6.5 or later for EKI-6333AC-2G and EKI-6333AC-2GD models
- 5. Upload and apply firmware version 1.2.2 or later for EKI-6333AC-1GPO model
- 6. Verify the upgrade was successful by checking the firmware version in the device management interface
- 7. After upgrade, verify that the edgserver service is no longer exposed to unauthenticated remote access if possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50372 — 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-50372 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