CVE-2020-10376
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 · uneditedTechnicolor TC7337NET 08.89.17.23.03 devices allow remote attackers to discover passwords by sniffing the network for an "Authorization: Basic" HTTP header.
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 confidenceThe Technicolor TC7337NET router firmware (version 08.89.17.23.03) transmits user credentials using HTTP Basic Authentication in cleartext. An attacker on the local network or positioned to sniff network traffic can capture the Base64-encoded 'Authorization: Basic' header and easily decode it to obtain plaintext passwords.
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= 08.89.17.23.03CVSS 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 the router modelCheck the device label or access the web management interface to confirm the model is Technicolor TC7337NETAffected if The device is a Technicolor TC7337NET router
-
Verify firmware versionAccess the router's web admin panel (typically at 192.168.0.1 or 192.168.1.1) and navigate to the status or firmware information page to find the exact version numberAffected if The firmware version is exactly 08.89.17.23.03
-
Confirm HTTP is used for loginAttempt to access the router's login page using HTTP (not HTTPS) - note whether the connection uses http:// rather than https://Affected if The login page is accessible over HTTP without redirect to HTTPS
-
Capture authentication trafficUse a network sniffer (such as Wireshark) or a browser's developer tools on a computer connected to the same network to capture the login request. Inspect the HTTP headers for an 'Authorization: Basic' headerAffected if The Authorization header is transmitted in plain HTTP (not encrypted) and contains Base64-encoded credentials
A user is affected if they are using a Technicolor TC7337NET router with firmware version 08.89.17.23.03 and the web management interface uses unencrypted HTTP for authentication, exposing credentials in Base64-encoded cleartext.
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.
From vendor dataEnable HTTPS/TLS for the router's web management interface to encrypt authentication traffic. If the device cannot support secure communications, segment it on an isolated VLAN to limit exposure and consider replacing with a supported device.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10376 — 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-2020-10376 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