dbcve.org
Tc8715d FirmwareOperating system · Technicolor

CVE-2023-47352

HIGH · 8.8 CVSS v3.1 Published 2024-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
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
Technicolor TC8715D devices have predictable default WPA2 security passwords. An attacker who scans for SSID and BSSID values may be able to predict these passwords.

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 confidence

Technicolor TC8715D devices generate default WPA2 WiFi passwords using a predictable algorithm based on SSID and BSSID (MAC address) values. An attacker can discover the network's SSID and BSSID through wireless reconnaissance and then calculate the default password, enabling unauthorized wireless access.

MitigationChange the default WPA2 password to a strong, randomly generated value through the router's administrative interface. Consider disabling SSID broadcast and upgrading to WPA3 if supported for additional security.

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
Tc8715d FirmwareOperating system
Affected:all versions

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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. Identify the device model
    Check the router label or administrative interface for the exact model number (TC8715D or TC8715D v5/v6)
    Affected if Device is a Technicolor TC8715D or TC8715D variant
  2. Check if SSID is still default
    View the wireless network name (SSID) broadcast by the device. Default SSIDs typically follow patterns like 'XFINITY', 'XFINITY-5G', or 'Technicolor' with numeric suffixes
    Affected if SSID matches the ISP default pattern and has not been renamed by the user
  3. Verify WPA2 password has been changed
    Access the router's web administrative interface (typically 10.0.0.1) and navigate to Wireless Settings. Compare the current WiFi password against any default or factory-set password patterns
    Affected if The WPA2 password is still set to the factory default value or follows a predictable pattern based on SSID/BSSID calculation
  4. Confirm BSSID is discoverable
    Use a wireless scanner or 'iwlist' / 'airodump-ng' command to capture the BSSID (MAC address) of the access point
    Affected if The BSSID is visible to wireless clients - this is required for an attacker to calculate the predicted password

You are affected if you use a Technicolor TC8715D device with factory-default WPA2 credentials still configured, as the password can be calculated from the SSID and BSSID values.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Change the default WPA2 password to a strong, randomly generated value through the router's administrative interface. Consider disabling SSID broadcast and upgrading to WPA3 if supported for additional security.

Recommended fix Moderate confidence
  1. Access the router's web management interface (typically at 192.168.0.1 or 192.168.1.1)
  2. Log in with the default administrator credentials (consult device documentation or check for default credentials on the device label)
  3. Navigate to the wireless security settings (Wireless or WLAN section)
  4. Change the WPA2 pre-shared key from the default to a strong, unique password of at least 12 characters using a mix of uppercase, lowercase, numbers, and special characters
  5. Apply the settings and reconnect all wireless devices using the new password
  6. Additionally, change the router's admin password from the default to prevent unauthorized access to configuration settings

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

Fix this in Tc8715d Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47352 — 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-47352 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