CVE-2024-36061
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-FIT devices through 1.1.30 allow blind OS command injection. This allows an attacker to execute arbitrary OS commands via shell metacharacters to the Ping and Speed Test utilities.
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 confidenceThe EnGenius EWS356-FIT wireless access point firmware through version 1.1.30 contains a blind OS command injection vulnerability in the Ping and Speed Test diagnostic utilities. Attackers can inject arbitrary OS commands via shell metacharacters because user input to these diagnostic features is not properly sanitized before being passed to system shell execution.
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
- 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 modelAccess the web management interface or check the device label to confirm the model is EWS356-FITAffected if Device is an EnGenius EWS356-FIT access point
-
Check firmware versionLog into the web management interface and navigate to System > Status or similar to view the firmware version. Compare against the affected range <= 1.1.30Affected if Firmware version is 1.1.30 or lower
-
Locate diagnostic utilitiesNavigate through the web management interface to find Ping and Speed Test diagnostic features, typically under Tools, Diagnostics, or Network Utilities sectionsAffected if Ping or Speed Test diagnostic utilities are present and accessible in the interface
-
Verify network exposureCheck if the management interface (HTTP/HTTPS on ports 80/443 or vendor-specific ports) is exposed to untrusted networks. Use firewall rules or network scans to confirm access restrictionsAffected if Management interface is accessible from untrusted/broadband-facing networks without VPN protection
A user is affected if they have an EnGenius EWS356-FIT device running firmware version 1.1.30 or lower with the Ping or Speed Test diagnostic utilities accessible to untrusted network 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.
From vendor dataImmediately restrict network access to the device management interface to trusted IPs only, or place behind a jump host. Contact EnGenius for firmware version 1.1.31 or later which should contain the patch. If no patch is available, consider replacing the device.
- Consultation4.0 h
- Implementation3.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,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36061 — 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-36061 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