# CVE-2020-11618: Hardcoded credentials in n/a

> Attackers on the local network can gain root access via hardcoded TELNET service enabled by default on Thomson and Philips set-top boxes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h2wr-mxwq-cxfr

## What is CVE-2020-11618?

CVE-2020-11618 is a high-severity vulnerability in n/a, published on 31 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

THOMSON THT741FTA 2.2.1 and Philips DTR3502BFTA DVB-T2 2.2.1 set-top boxes have their TELNET service hardcoded to start on boot, which allows an attacker on the local network to achieve root access via the TELNET protocol.

## Which versions are affected by CVE-2020-11618?

It affects 2 products.


Products: Philips Dtr3502bfta Dvb-T2 Firmware, Thomsonstb Tht741fta Firmware.

## How do I fix CVE-2020-11618?

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

## Is CVE-2020-11618 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11617](https://insights.sbomify.com/CVE-2020-11617/): Security feature bypass in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11618 and fix it if it is affected.

What it is: CVE-2020-11618 is a high-severity vulnerability in n/a, published on 31 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11618 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-2020-11618/ (Markdown: https://insights.sbomify.com/CVE-2020-11618/index.md)
```

## Sources

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

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