# CVE-2023-4617: Gaining remote control over Govee devices

> Remote attackers can control other users' Govee devices by manipulating HTTP POST parameters in the mobile application.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/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:** 19 Dec 2024
- **Updated:** 20 Dec 2024
- **Also known as:** GHSA-59pp-rvhc-93rh

## What is CVE-2023-4617?

CVE-2023-4617 is a critical missing authorization vulnerability in Govee Home, published on 19 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect authorization vulnerability in HTTP POST method in Govee Home application on Android and iOS allows remote attacker to control devices owned by other users via changing "device", "sku" and "type" fields' values. 
This issue affects Govee Home applications on Android and iOS in versions before 5.9.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2023-4617 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4617 is a critical missing authorization vulnerability in Govee Home, published on 19 Dec 2024. 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-4617 in the wild and no public exploit code.

Affected product: Govee Home. 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-4617/ (Markdown: https://insights.sbomify.com/CVE-2023-4617/index.md)
```

## Sources

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

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