CVE-2024-50360
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 "snmp_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 · moderate confidenceOS command injection vulnerability in Advantech EKI-6333AC wireless access point series. The 'snmp_apply' API does not properly sanitize multiple parameters before concatenating them into OS-level commands, allowing authenticated attackers to execute arbitrary commands on the underlying operating system.
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 device modelAccess the device web interface or check the physical label to confirm the exact model: EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPOAffected if Device is any of these three models
-
Check firmware versionNavigate to the device web interface System Status or Firmware Upgrade page, or use SNMP or CLI to retrieve the firmware version. Compare against thresholds: 1.6.5 for 2G/2GD models, 1.2.2 for 1GPO modelAffected if Firmware version is below 1.6.5 for 2G/2GD, or below 1.2.2 for 1GPO
-
Verify SNMP service statusCheck if SNMP is enabled on the device through the web interface under SNMP Settings or by querying SNMP (snmpwalk) the deviceAffected if SNMP is enabled and accessible to the attacker
-
Confirm management interface accessibilityDetermine if the device web management interface (HTTP/HTTPS) is reachable from untrusted networks by reviewing firewall rules or network ACLsAffected if Management interface is exposed to untrusted networks without IP restrictions
Device is affected if it is an EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO with firmware below the respective threshold and SNMP is enabled and reachable.
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 to versions beyond 1.6.3 (for EKI-6333AC-2G/2GD) and 1.2.1 (for EKI-6333AC-1GPO). If updates are unavailable, restrict network access to the device's management interface to trusted sources only.
EKI-6333AC-2G: firmware >= 1.6.5 | EKI-6333AC-2GD: firmware >= 1.6.5 | EKI-6333AC-1GPO: firmware >= 1.2.2
- 1. Identify the specific model (EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO) of the affected Advantech device
- 2. Check the current firmware version via the device web interface or CLI
- 3. Download the firmware update from the official Advantech support portal (www.advantech.com) - ensure version 1.6.5 or later for EKI-6333AC-2G/2GD, or version 1.2.2 or later for EKI-6333AC-1GPO
- 4. Back up the current device configuration before upgrading
- 5. Upload the firmware file through the device's web management interface or via TFTP/FTP as documented in the device manual
- 6. Wait for the upgrade to complete and the device to reboot
- 7. Verify the new firmware version is installed and the SNMP service is functioning properly
- 8. Confirm the vulnerability is remediated by checking that SNMP parameters are now properly sanitized
Generated from the published advisory — verify against the referenced sources before acting.
- 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-50360 — 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-50360 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