Smart Plug 10a FirmwareOperating system · Quboworld

CVE-2023-36160

MEDIUM · 5.5 CVSS v3.1 Published 2023-09-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
An issue was discovered in Qubo Smart Plug10A version HSP02_01_01_14_SYSTEM-10 A, allows local attackers to gain sensitive information and other unspecified impact via UART console.

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 confidence

The Qubo Smart Plug10A (version HSP02_01_01_14_SYSTEM-10 A) contains an exposed UART console interface that allows local attackers with physical access to the device to retrieve sensitive information. This vulnerability stems from debug UART pins left accessible on the PCB in production firmware, enabling direct communication with the device's console without authentication.

MitigationSecure or disable the UART debug interface in production firmware by removing console output, implementing authentication, or physically disabling the UART pins. Consider moving to a secure boot process that does not expose debugging interfaces.

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
Smart Plug 10a FirmwareOperating system
Affected:= hsp02_01_01_14_system-10_a

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device firmware version
    Check the firmware version of your Qubo Smart Plug 10A device. This may be visible on the device label, in the Quboworld app device information, or via firmware extraction from the device firmware image.
    Affected if The firmware version matches exactly: HSP02_01_01_14_SYSTEM-10_a (or is an earlier version if the vulnerable configuration was present)
  2. Physically inspect for exposed UART pins
    Open the device casing and examine the PCB for exposed UART pins (typically 4 pins in a row: TX, RX, GND, VCC). These are usually located near the edge of the PCB or near the microcontroller.
    Affected if Debug UART pins (TX, RX, GND, VCC) are physically accessible and exposed on the PCB without physical barriers or epoxy coating
  3. Test console access via UART interface
    Connect a USB-to-serial adapter to the exposed UART pins (TX to RX, RX to TX, GND to GND). Use terminal software (e.g., PuTTY, minicom) to connect at common baud rates (9600, 57600, 115200). Observe if a console prompt or shell appears without any authentication requirement.
    Affected if The UART console provides direct access to a shell or command prompt without requiring any username or password authentication
  4. Verify console has privileged access
    Once connected via UART, attempt to run privileged commands (such as whoami, id, cat /etc/passwd) to determine if the console provides root or administrator-level access.
    Affected if The UART console grants root or administrator-level access without authentication

You are affected if you own a Qubo Smart Plug 10A with firmware HSP02_01_01_14_SYSTEM-10_a and the device has physically accessible UART debug pins that grant unauthenticated console or shell access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Secure or disable the UART debug interface in production firmware by removing console output, implementing authentication, or physically disabling the UART pins. Consider moving to a secure boot process that does not expose debugging interfaces.

Fix this in Smart Plug 10a Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36160 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-36160 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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