CVE-2024-50362
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 source of the vulnerability relies on multiple parameters belonging to the "connection_profile_apply" API which are not properly sanitized before being concatenated to OS level commands.
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 point firmware. Multiple parameters in the 'connection_profile_apply' API are concatenated directly to OS-level shell commands without input sanitization, allowing authenticated attackers to inject and execute arbitrary operating system commands.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 device modelLocate the physical access point or check the web interface system information page for the model number EKI-6333AC (variants include 2G, 2GD, or 1GPO)Affected if The device is not an Advantech EKI-6333AC variant
-
Determine the installed firmware versionAccess the device web interface and navigate to Status or System Information page to view the firmware version, or check the device label/CLI if availableAffected if Unable to retrieve firmware version from the device
-
Compare firmware version against affected rangesCheck the firmware version against these ranges: EKI-6333AC-2G < 1.6.5, EKI-6333AC-2GD < 1.6.5, or EKI-6333AC-1GPO < 1.2.2Affected if The installed version falls within any of these affected ranges
-
Verify remote management accessibilityConfirm the device web interface (port 80/443) or API endpoint is accessible from network segments. Check if the 'connection_profile_apply' endpoint respondsAffected if The device management interface is exposed to untrusted networks and the firmware version is affected
The environment is affected if an Advantech EKI-6333AC device (2G/2GD/1GPO variant) is running firmware version below 1.6.5/1.2.2 respectively AND the device management interface is network-accessible to attackers.
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 if available (EKI-6333AC-2G/2GD >1.6.3, EKI-6333AC-1GPO >v1.2.1). If no patch available, restrict administrative access to trusted networks only and disable unused management interfaces.
EKI-6333AC-2G/2GD: firmware 1.6.5; EKI-6333AC-1GPO: firmware 1.2.2
- Identify the specific model of the affected Advantech EKI device (EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO)
- Navigate to the device's web administration interface or console
- Locate the firmware upgrade section in the device settings
- Download the firmware update from Advantech's official support website - ensure the version is 1.6.5 for EKI-6333AC-2G/EKI-6333AC-2GD or 1.2.2 for EKI-6333AC-1GPO
- Upload the firmware file to the device and initiate the upgrade process
- Wait for the upgrade to complete and the device to reboot
- Verify the firmware version has been successfully updated to the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50362 — 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-50362 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