CVE-2024-45242
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 ENH1350EXT A8J-ENH1350EXT devices through 3.9.3.2_c1.9.51 allow (blind) OS Command Injection via shell metacharacters to the Ping or Speed Test utility. During the time of initial setup, the device creates an open unsecured network whose admin panel is configured with the default credentials of admin/admin. An unauthorized attacker in proximity to the Wi-Fi network can exploit this window of time to execute arbitrary OS commands with root-level permissions.
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 confidenceEnGenius ENH1350EXT wireless access points through version 3.9.3.2_c1.9.51 contain a blind OS command injection vulnerability in the Ping and Speed Test utilities. During initial setup, the device broadcasts an open unsecured Wi-Fi network with default admin credentials (admin/admin), allowing any attacker within Wi-Fi range to inject arbitrary OS commands via shell metacharacters, executing with root-level privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Identify device model and firmware versionAccess the device web interface or check via SNMP/CLI to retrieve the exact hardware model (ENH1350EXT) and firmware version stringAffected if Firmware version is 3.9.3.2_c1.9.51 or any earlier version (versions through 3.9.3.2_c1.9.51 are affected)
-
Confirm default admin credentials are activeAttempt to authenticate to the device admin interface using the default credentials admin/admin, or check if the credential has been changed from defaultsAffected if The default username 'admin' with password 'admin' still provides administrative access to the device
-
Determine if device is in initial setup stateScan for wireless networks; the vulnerable setup network is an open (unsecured) Wi-Fi network typically broadcast by the device during first-time configurationAffected if The device is broadcasting an open unsecured Wi-Fi network and has not completed initial setup configuration
-
Verify Ping or Speed Test utility accessibilityLog into the device admin interface and navigate to the Ping or Speed Test diagnostic utilities, or observe if these features are exposed and accessibleAffected if The Ping or Speed Test diagnostic utilities are accessible and can accept user-supplied input
Your environment is affected if you have an EnGenius ENH1350EXT device running firmware version 3.9.3.2_c1.9.51 or earlier, with default admin credentials still active, and the device is in or has completed initial setup with the Ping/Speed Test utilities accessible.
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 change default admin credentials after device setup, disable the open setup network, and apply vendor firmware patches when available. Network operators should isolate these devices during the vulnerable setup window and consider compensating controls such as WPA enterprise authentication and network segmentation.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45242 — 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-45242 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