CVE-2019-15806
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 · uneditedCommScope ARRIS TR4400 devices with firmware through A1.00.004-180301 are vulnerable to an authentication bypass to the administrative interface because they include the current base64 encoded password within http://192.168.1.1/basic_sett.html. Any user connected to the Wi-Fi can exploit this.
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 CommScope ARRIS TR4400 router with firmware through A1.00.004-180301 exposes the base64 encoded administrative password in plain text at the URL http://192.168.1.1/basic_sett.html. Any user connected to the Wi-Fi network can access this page and decode the password to gain full administrative access to the device without authentication.
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<= a1.00.004-180301CVSS 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.0/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.
-
Confirm router model is TR4400Access the router admin interface at http://192.168.1.1 and identify the device model. Look for 'ARRIS TR4400' or 'CommScope TR4400' in the device status or information page.Affected if The device is an ARRIS or CommScope TR4400 router
-
Check firmware versionIn the router admin interface, navigate to the status or firmware information page and record the firmware version number. Compare it against 'a1.00.004-180301' and earlier versions.Affected if The installed firmware version is a1.00.004-180301 or any version prior to it
-
Access the vulnerable endpointOpen a web browser or use curl and navigate to http://192.168.1.1/basic_sett.html while connected to the router network. Observe whether the page loads without requiring authentication.Affected if The basic_sett.html page loads without any login prompt
-
Verify credential exposureIf the page loads, examine the HTML source or response body for base64-encoded strings. Use a base64 decoder to test whether any encoded value decodes to an administrative password.Affected if Base64-encoded password strings are visible in plain text on the page without authentication
You are affected if the device is a TR4400 router running firmware a1.00.004-180301 or earlier, and the endpoint http://192.168.1.1/basic_sett.html is accessible without authentication and exposes base64-encoded credentials.
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 dataApply vendor firmware update if available; if no update exists, isolate the device on a restricted network segment and change the exposed administrative password immediately to limit exposure.
- Consultation3.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15806 — 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-2019-15806 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