CVE-2018-20444
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 CGA0111 CGA0111E-ES-13-E23E-c8000r5712-170217-0829-TRU devices allow remote attackers to discover Wi-Fi credentials via iso.3.6.1.4.1.4413.2.2.2.1.5.4.1.14.1.3.10001 and 1.3.6.1.4.1.4413.2.2.2.1.18.1.2.3.4.1.2.10001 SNMP requests.
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 confidenceUnauthenticated remote attackers can retrieve Wi-Fi credentials (SSID and PSK/password) from Technicolor CGA0111 routers via specific SNMP OID queries. The vulnerable OIDs expose sensitive wireless configuration data 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= cga0111e-es-13-e23e-c8000r5712-170217-0829-truCVSS 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.
-
Identify device modelAccess the router web interface or check the device label to confirm the model is Technicolor CGA0111Affected if Device is not a Technicolor CGA0111 router, then it is not affected by this specific CVE
-
Check firmware versionLog into the router admin panel or use SNMP to query the firmware version OID, then compare it to the affected version cga0111e-es-13-e23e-c8000r5712-170217-0829-truAffected if Firmware version exactly matches cga0111e-es-13-e23e-c8000r5712-170217-0829-tru, the router is likely affected
-
Verify SNMP is enabledAttempt to send an SNMP GET request to the router on UDP port 161 using a tool like snmpwalk or snmpgetAffected if SNMP responds to requests, indicating it is enabled and accessible
-
Test for unauthenticated SNMP accessSend SNMP queries using default community strings such as 'public' or 'private' without any authentication credentialsAffected if SNMP queries succeed with default community strings, indicating unauthenticated access is possible
-
Query wireless configuration OIDsUse snmpwalk to enumerate SNMP OIDs related to wireless SSID and PSK settings (for example, OIDs under the wireless MIB or vendor-specific branches)Affected if The queries return SSID and PSK values, confirming the vulnerable OIDs are exposed
A Technicolor CGA0111 router running the specific affected firmware with SNMP enabled and accessible without authentication is vulnerable to credential exposure via SNMP queries.
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 dataImmediately restrict SNMP access to trusted management networks only, block UDP port 161 from untrusted sources at network perimeter, and contact vendor for firmware updates.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20444 — 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-2018-20444 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