CVE-2024-50373
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 "restore_config_from_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 confidenceAn OS command injection vulnerability (CWE-78) exists in Advantech EKI-6333AC wireless access point firmware versions <= 1.6.3 (2G/2GD models) and <= 1.2.1 (1GPO model). The flaw resides in the 'restore_config_from_utility' operation within the unauthenticated 'edgserver' service, 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 device model and firmware versionAccess the device web interface or check the system information page, or use the command line interface (if available) to retrieve the firmware version. Look for the exact version number displayed in the device status or about section.Affected if The device model is Eki 6333ac 2g, Eki 6333ac 2gd, or Eki 6333ac 1gpo and the firmware version is below 1.6.5 (for 2g/2gd models) or below 1.2.2 (for 1gpo model).
-
Locate the edgserver serviceCheck the device's running processes or services list. On the device shell (if accessible), look for a process named 'edgserver' or check the service initialization scripts.Affected if The 'edgserver' service is present and running on the device.
-
Determine if edgserver is network accessibleCheck the device's network configuration and firewall rules. Look for open ports associated with edgserver (commonly ports 80, 443, or a custom port). Use a network scanner to probe the device from an external network perspective.Affected if The edgserver service is listening on a network interface that is accessible from untrusted networks (not isolated behind a firewall or VPN).
-
Verify restore_config_from_utility functionalityIf you have administrative access, examine the device's configuration backup/restore functions. Check if the 'restore_config_from_utility' operation is present in the edgserver service API or web interface.Affected if The restore_config_from_utility operation is available and exposed without authentication requirements.
A device is affected if it is an Advantech EKI-6333 series model running firmware below the specified version thresholds AND has the edgserver service enabled and network-accessible.
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-supplied firmware updates when available; as an interim compensating control, restrict network access to the edgserver service using firewall rules or network segmentation to prevent unauthenticated external access.
EKI-6333AC-2G/2GD: firmware >= 1.6.5; EKI-6333AC-1GPO: firmware >= 1.2.2
- 1. Identify the specific model number (EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO)
- 2. Check the current firmware version running on the device
- 3. Download the fixed firmware from Advantech's official support website: https://www.advantech.com/ (support/downloads or product support pages)
- 4. For EKI-6333AC-2G and EKI-6333AC-2GD models, upgrade to firmware version 1.6.5 or later
- 5. For EKI-6333AC-1GPO model, upgrade to firmware version 1.2.2 or later
- 6. Follow Advantech's published firmware upgrade procedure for the specific model (typically via web UI or TFTP)
- 7. Verify the upgrade was successful by checking the new firmware version
- 8. Confirm the 'edgserver' service is now properly secured or verify the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50373 — 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-50373 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