CVE-2024-50374
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 "capture_packages" 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 confidenceOS Command Injection vulnerability in Advantech EKI-6333AC wireless access points allows remote unauthenticated attackers to execute arbitrary OS commands with root privileges via the 'capture_packages' operation in the unauthenticated 'edgserver' service.
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 system information pages for the exact model number (Eki 6333ac 2g, 2gd, or 1gpo) and installed firmware version. Compare against affected versions: < 1.6.5 for 2g/2gd models, < 1.2.2 for 1gpo model.Affected if Device model is Eki 6333ac 2g, 2gd, or 1gpo and firmware version is below 1.6.5 (for 2g/2gd) or below 1.2.2 (for 1gpo)
-
Verify edgserver service is running and exposedCheck if the edgserver service is listening on network ports (commonly port 8080 or similar). Use 'netstat -an' or 'ss -tlnp' from the device CLI or check open ports from the web interface under network settings.Affected if The edgserver service is accessible from network interfaces other than localhost
-
Confirm capture_packages operation is accessible without authenticationAttempt to access the capture_packages endpoint (typically /capture_packages or similar URL path) on the edgserver service without providing credentials. Check if the request is accepted without authentication.Affected if The capture_packages operation accepts requests without authentication
-
Check network exposure of the deviceReview firewall rules and network configuration to determine if the edgserver service port is exposed to untrusted networks (WAN, internet, or external network segments).Affected if The device management interface or edgserver service is reachable from untrusted networks
You are affected if you have an Advantech EKI-6333AC device (2g, 2gd, or 1gpo model) running firmware below the thresholds (1.6.5 or 1.2.2 respectively), with the edgserver service exposed to network where unauthenticated attackers can reach the capture_packages operation.
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.
From vendor data1.2.21.6.5
Isolate affected devices from untrusted networks immediately; contact Advantech for firmware patches and apply vendor-provided updates once available.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50374 — 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-50374 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