Mini Smart Wi-fi Plug Firmware: Incorrect Permission Assignment for Critical Resource
CVE-2023-42189 is a high-severity incorrect permission assignment for critical resource vulnerability in Mini Smart Wi-fi Plug Firmware from Tapo, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 1.02% chance of exploitation within 30 days, higher than 64% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Mini Smart Wi-fi Plug Firmware you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Tapo | Mini Smart Wi-fi Plug Firmware | Not specified in the record | Not stated |
| Nanoleaf | Lightstrip Firmware | 3.5.10 | Not stated |
| Govee | Led Strip Firmware | 3.00.42 | Not stated |
| Switchbot | Hub2 Firmware | 1.0-0.8 | Not stated |
| Phillips | Hue Bridge Firmware | 1.59.1959097030 | Not stated |
| Yeelight | Smart Lamp Firmware | 1.12.69 | Not stated |
| TP-Link | Smart Plug Firmware | Not specified in the record | Not stated |
| Orein | Smart Bulb Firmware | Not specified in the record | Not stated |
| Eve | Eve Door And Window Firmware | Not specified in the record | Not stated |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
Official description
Insecure Permissions vulnerability in Connectivity Standards Alliance Matter Official SDK v.1.1.0.0 , Nanoleaf Light strip v.3.5.10, Govee LED Strip v.3.00.42, switchBot Hub2 v.1.0-0.8, Phillips hue hub v.1.59.1959097030, and yeelight smart lamp v.1.12.69 allows a remote attacker to cause a denial of service via a crafted script to the KeySetRemove function.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Permission Assignment for Critical Resource
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
How developers prevent this class of flaw
- When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
- Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
- During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- github.com/IoT-Fuzz/IoT-Fuzz/blob/main/Remove%20Key%20Set%20Vulnerability%20Report.pdfThird Party Advisory
- github.com/project-chip/connectedhomeip/issues/28518Issue Tracking, Third Party Advisory
- github.com/project-chip/connectedhomeip/issues/28679Issue Tracking, Third Party Advisory
Recent Incorrect Permission Assignment for Critical Resource vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.1 High severity
- 7.5 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.