CVE-2023-36161
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 · uneditedAn issue was discovered in Qubo Smart Plug 10A version HSP02_01_01_14_SYSTEM-10A, allows attackers to cause a denial of service (DoS) via Wi-Fi deauthentication.
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 Qubo Smart Plug 10A (HSP02_01_01_14_SYSTEM-10A) is vulnerable to Wi-Fi deauthentication attacks, allowing unauthenticated attackers to disconnect the device from the network by sending spoofed deauthentication frames. This DoS condition renders the smart plug non-functional until reconnected manually or automatically.
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= hsp02_01_01_14_system-10aCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 modelLocate the physical Qubo Smart Plug 10A and check the product labeling or packaging for the model number HSP02_01_01_14_SYSTEM-10AAffected if The device is not a Qubo Smart Plug 10A with model HSP02_01_01_14_SYSTEM-10A
-
Check the installed firmware versionAccess the Quboworld app or the device settings interface to view the firmware version. Navigate to device information or settings menu where the firmware version is displayedAffected if The firmware version displayed is exactly hsp02_01_01_14_system-10a (exact match)
-
Verify management frame protection capabilityCheck the device settings or Quboworld app for any option related to 802.11w, Protected Management Frames (PMF), or Wi-Fi security enhancements. Look in the Wi-Fi settings or advanced network settings of the smart plugAffected if There is no option available to enable 802.11w or Protected Management Frames in the device settings (the firmware lacks this capability)
-
Assess network vulnerability exposureObserve the smart plug on the Wi-Fi network. Use a wireless packet analyzer to monitor if deauthentication frames are being processed without validation, or simply note that the device can be disconnected by unauthorized deauthentication frames sent from within radio rangeAffected if The device responds to and processes unauthenticated deauthentication frames, allowing anyone nearby to disconnect it from the network
You are affected if you have a Qubo Smart Plug 10A running firmware version hsp02_01_01_14_system-10a, which lacks 802.11w support and accepts unauthenticated deauthentication frames.
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 dataImplement 802.11w (management frame protection) in the device firmware to reject unauthenticated deauthentication/disassociation frames, and enable protected management frames on the associated wireless network.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36161 — 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-2023-36161 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