CVE-2024-23726
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 · uneditedUbee DDW365 XCNDDW365 devices have predictable default WPA2 PSKs that could lead to unauthorized remote access. A remote attacker (in proximity to a Wi-Fi network) can derive the default WPA2-PSK value by observing a beacon frame. A PSK is generated by using the first six characters of the SSID and the last six of the BSSID, decrementing the last digit.
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 confidenceUbee DDW365 XCNDDW365 devices generate default WPA2-PSKs using a predictable algorithm: the first six characters of the SSID concatenated with the last six characters of the BSSID, with the final digit decremented by one. An attacker in Wi-Fi range can capture a beacon frame, extract the SSID and BSSID, compute the PSK using this algorithm, and gain unauthorized network access.
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 dataall versionsCVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 the device modelCheck the label on the router or access the router's web interface (typically at 192.168.0.1 or 192.168.1.1) to confirm the model number is Ubee DDW365 or XCNDDW365Affected if The device is not a Ubee DDW365 or XCNDDDW365 model
-
Locate the default SSIDAccess the router's wireless settings page and record the current SSID (wireless network name)Affected if The SSID follows a pattern where the first six characters represent the default network identifier
-
Locate the BSSIDUse a wireless scanner tool (such as inSSIDer, WiFi Analyzer, or 'ipconfig /all' on Windows, 'iwconfig' on Linux) to find the BSSID (wireless access point MAC address) of the networkAffected if A valid BSSID is retrieved for the wireless interface
-
Verify the PSK against the predictable algorithmConstruct the suspected default PSK by taking the first six characters of the SSID, concatenating the last six characters of the BSSID, and subtracting one from the final digit. Compare this calculated value to the current Wi-Fi password.Affected if The current WPA2-PSK matches the algorithm: [first 6 chars of SSID] + [last 6 chars of BSSID] with final digit decremented by one
-
Confirm if default credentials are still in useCheck whether the Wi-Fi password has ever been changed from the factory defaultAffected if The Wi-Fi PSK has not been changed and still uses the predictable default pattern derived from SSID and BSSID
A defender is affected if they operate a Ubee DDW365 device and the current Wi-Fi password matches the predictable default PSK algorithm derived from concatenating the first six SSID characters with the last six BSSID characters (minus one from the final digit).
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 the default Wi-Fi password to a strong, randomly-generated PSK not derived from SSID or BSSID values. Contact Ubee for firmware updates that implement cryptographically secure PSK generation.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23726 — 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-23726 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