# CVE-2018-20441: Information disclosure in n/a

> Remote attackers can retrieve Wi-Fi credentials from Technicolor TC7200 devices via specific SNMP requests, exposing network access details.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Dec 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-x655-8w7q-xmqg

## What is CVE-2018-20441?

CVE-2018-20441 is a critical vulnerability in n/a, published on 25 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Technicolor TC7200.TH2v2 SC05.00.22 devices allow remote attackers to discover Wi-Fi credentials via iso.3.6.1.4.1.2863.205.10.1.30.4.1.14.1.3.32 and iso.3.6.1.4.1.2863.205.10.1.30.4.2.4.1.2.32 SNMP requests.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2018-20441?

It affects 1 product.


Products: Technicolor Tc7200.th2v2 Firmware.

## How do I fix CVE-2018-20441?

No fix has been published for CVE-2018-20441 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-20441 being exploited?

There is no known exploitation of CVE-2018-20441 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20441 and fix it if it is affected.

What it is: CVE-2018-20441 is a critical vulnerability in n/a, published on 25 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20441 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-20441/ (Markdown: https://insights.sbomify.com/CVE-2018-20441/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-20441
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-20441
- OSV: https://osv.dev/vulnerability/CVE-2018-20441

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-20441/
Summaries are generated and may contain mistakes; the official description above is the record.