CVE-2023-4617
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 · uneditedIncorrect 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.
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 confidenceIncorrect authorization in the Govee Home mobile application's HTTP POST handler allows an attacker to control devices owned by other users by manipulating the 'device', 'sku', and 'type' field values in requests, bypassing proper device ownership validation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/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.
-
Check Govee Home app version on AndroidOpen device Settings > Apps > Govee Home, or use 'adb shell dumpsys package com.govee.home' to view version infoAffected if Version displayed is below 5.9 (e.g., 5.8.x or earlier)
-
Check Govee Home app version on iOSOpen Settings > General > iPhone Storage > Govee Home, or view in App Store purchase historyAffected if Version displayed is below 5.9 (e.g., 5.8.x or earlier)
-
Verify HTTP POST control requests are being sentUse a network proxy (e.g., Burp Suite, mitmproxy) to intercept traffic from the Govee Home app while controlling a device; examine POST requests to the control endpointAffected if Requests contain manipulable 'device', 'sku', and 'type' fields without additional ownership verification in the response
User is affected if Govee Home application version is below 5.9 and the app is used to control IoT devices, as the authorization bypass in the HTTP POST handler permits control of devices not owned by the user.
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.
dbcve · scopedUpgrade Govee Home application to version 5.9 or later; additionally, implement server-side validation ensuring users can only control devices they legitimately own by verifying device-user associations before processing control commands.
Govee Home version 5.9 or later for Android and iOS
- Open Google Play Store (Android) or App Store (iOS) on your device
- Search for "Govee Home"
- Tap Update to install version 5.9 or later
- Alternatively, enable automatic app updates to ensure you receive future security patches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4617 — 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-4617 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