# CVE-2023-42189: Denial of service in n/a

> Remote attackers can cause denial of service on Matter SDK-based smart home devices via a crafted script to the KeySetRemove function.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2023
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-gg6j-gxcg-jjcm

## What is CVE-2023-42189?

CVE-2023-42189 is a high-severity denial of service vulnerability in n/a, published on 10 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2023-42189?

It affects 9 products.


Products: Eve Eve Door and Window Firmware, Govee Led Strip Firmware, Nanoleaf Lightstrip Firmware, Orein Smart Bulb Firmware, Phillips Hue Bridge Firmware, Switchbot Hub2 Firmware, Tapo Mini Smart Wi-Fi Plug Firmware, Tp-Link Smart Plug Firmware, Yeelight Smart Lamp Firmware.

## How do I fix CVE-2023-42189?

No fix has been published for CVE-2023-42189 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-42189 being exploited?

There is no known exploitation of CVE-2023-42189 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-42189 and fix it if it is affected.

What it is: CVE-2023-42189 is a high-severity denial of service vulnerability in n/a, published on 10 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-42189 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-42189/ (Markdown: https://insights.sbomify.com/CVE-2023-42189/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-42189
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-42189
- OSV: https://osv.dev/vulnerability/CVE-2023-42189

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-42189/
Summaries are generated and may contain mistakes; the official description above is the record.