CVE-2024-31976
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 · uneditedEnGenius EWS356-FIR 1.1.30 and earlier devices allow a remote attacker to execute arbitrary OS commands via the Controller connectivity parameter.
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 confidenceThis is a command injection vulnerability in EnGenius EWS356-FIR wireless access point firmware versions 1.1.30 and earlier. Attackers can inject arbitrary OS commands through the Controller connectivity parameter in the web management interface, achieving remote code execution on the affected device.
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.1.30CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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.
-
Confirm device model is EWS356-FIRAccess the device web management interface and navigate to the System Status or Device Information page to verify the exact model number displays as EWS356-FIRAffected if Device model is not EWS356-FIR (different models may have different vulnerabilities)
-
Check firmware version through web interfaceLog into the web management interface and locate the firmware version in System Status, Device Info, or About section. Compare the displayed version number against 1.1.30Affected if Firmware version displayed is 1.1.30 or earlier (any version <= 1.1.30)
-
Check firmware version via SNMP if web access unavailableUse an SNMP tool (such as snmpwalk) to query the device OID sysDescr or entPhysicalSoftwareRev if SNMP is enabled on the deviceAffected if SNMP returns a firmware version string indicating 1.1.30 or earlier
-
Determine if web management interface is network-accessibleAttempt to reach the device web interface from an untrusted network segment or perform a port scan (typically ports 80/443) against the device IP address from an external locationAffected if The web management interface is accessible from untrusted networks (indicates potential remote exploitation path)
-
Identify Controller connectivity configurationIn the web interface, navigate to Network Settings, Wireless Settings, or Controller configuration section and locate any field labeled Controller, Controller IP, or Controller connectivityAffected if The Controller connectivity parameter exists and is user-configurable (this is the injection point)
A defender is affected if the device is an EWS356-FIR running firmware version 1.1.30 or earlier AND the web management interface (containing the vulnerable Controller parameter) is accessible to untrusted networks.
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 dataApply vendor firmware updates when available. Until then, restrict network access to the device management interface to trusted sources only, preferably through VLAN segmentation or firewall rules, as this vulnerability is exploitable remotely.
- Consultation3.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31976 — 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-31976 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