dbcve.org
Chromecast FirmwareOperating system · Google

CVE-2023-48417

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-11
Fix available
A fix is available. Upgrade to 2023-10-01 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Missing Permission checks resulting in unauthorized access and Manipulation in KeyChainActivity Application

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 confidence

Missing authorization checks in the KeyChainActivity application allow unauthenticated attackers to access and manipulate sensitive keychain/credential data without proper permission validation. The vulnerability stems from unprotected API endpoints or functions that fail to verify user permissions before granting access to credential storage and manipulation operations.

MitigationImplement robust permission checks on all access points to keychain data, enforce proper authentication and authorization controls, and validate user permissions before allowing any access or modification operations.

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
Chromecast FirmwareOperating system
Affected:< 2023-10-01

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine Chromecast firmware version
    Open Google Home app, select your device, tap the gear icon for device settings, scroll to 'Technical details' to find the firmware version or cast firmware version
    Affected if The firmware version date is before October 1, 2023 (2023-10-01)
  2. Confirm KeyChainActivity component presence
    Access the device's system information or diagnostic page (typically via chrome://inspect or developer debugging tools if enabled) and search for processes or components named KeyChainActivity or keychain-related modules
    Affected if The KeyChainActivity component is present and running on the device
  3. Verify API endpoint accessibility
    If you have network access to the device, attempt to reach known keychain-related API endpoints (such as /keychain/ or /cryptauth/ endpoints) without providing any authentication credentials
    Affected if Requests to keychain-related endpoints return data or successful responses without requiring authentication
  4. Review access logs for keychain operations
    Check any available device logs, system logs, or security audit logs for access attempts to keychain or credential storage functions, noting whether unauthenticated requests are logged as successful
    Affected if Logs show successful keychain access attempts without proper authorization validation

Your Chromecast is affected if the firmware predates October 2023 AND the KeyChainActivity component is present and accessible without authentication checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2023-10-01 or later
Fixed in 2023-10-01
Interim mitigation

Implement robust permission checks on all access points to keychain data, enforce proper authentication and authorization controls, and validate user permissions before allowing any access or modification operations.

Recommended fix High confidence

Chromecast firmware version 2023-10-01 or later

  1. Ensure your Chromecast device is connected to the internet and powered on
  2. Open the Google Home app on your smartphone or tablet
  3. Select your Chromecast device from the list of available devices
  4. Tap the device settings (gear icon)
  5. Scroll down to device information and verify the firmware version is 2023-10-01 or later
  6. If a firmware update is available, the device should automatically update when connected to the internet; ensure automatic updates are not disabled in device settings
  7. If the firmware version is still below 2023-10-01 and no update is offered, try restarting the device and checking again, or factory reset the device and set it up again to trigger the update
Caveat Firmware updates are generally backward compatible; no known breaking changes for end users

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chromecast Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-48417 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-48417 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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