CVE-2023-48419
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 · uneditedAn attacker in the wifi vicinity of a target Google Home can spy on the victim, resulting in Elevation of Privilege
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 confidenceA critical vulnerability in Google Home allows an attacker within WiFi range to gain elevated privileges and spy on victims. The attack exploits the local network adjacency to compromise the device, likely through an authentication or authorization flaw in the Google Home's local API.
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< 2.58< 2.58< 2.58< 2.58CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Identify your Google Home device modelLocate the physical device or open the Google Home app, then check the device settings or packaging to confirm the exact model (Nest Audio, Nest Mini, Home Mini, or Home)Affected if The device is one of the four affected models: Nest Audio, Nest Mini, Home Mini, or Home
-
Check the installed firmware versionOpen the Google Home app, select your device, tap the gear icon (settings), then go to Device information to view the firmware version numberAffected if The displayed firmware version is lower than 2.58 (for example, 2.55, 2.56, or 2.57)
-
Verify network accessibility to the local APIOn a device connected to the same WiFi network as your Google Home, attempt to reach the device's local API port (typically port 8008 or 8443) using a web browser or curl command to https://[device-ip]:8008/setup/eureka_infoAffected if The local API responds and returns device information, meaning the device is reachable from the local network and could be exploited if the firmware is vulnerable
-
Compare your version against affected rangeIf you obtained the firmware version through the app or local API, compare it numerically to 2.58 - any version starting with 2.5x below 2.58, or earlier version branches, are affectedAffected if Your firmware version is less than 2.58, regardless of whether you confirmed local API accessibility
You are affected if you have a Google Nest Audio, Nest Mini, Home Mini, or Home device running firmware version lower than 2.58 and that device is accessible on your local network.
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 · scoped2.58
Apply available Google Home firmware updates immediately and ensure strong WiFi network segmentation to limit exposure to nearby attackers.
Firmware version 2.58 or later for Nest Audio, Nest Mini, Home Mini, and Home devices
- Ensure your Nest device is connected to a stable internet connection
- Open the Google Home app on your mobile device
- Select the affected Nest device from the device list
- Navigate to the device settings
- Check for firmware updates and allow the device to update to version 2.58 or later
- Verify the firmware version has been updated to 2.58 or higher after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-48419 — 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-48419 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