# CVE-2020-12773: Realtek ADSL/PON Modem SoC - Security Misconfiguration

> Attackers can execute arbitrary commands remotely on Realtek ADSL/PON Modem SoC firmware by exploiting a default password in the network monitoring tool.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wmgf-fhc9-5pvg

## What is CVE-2020-12773?

CVE-2020-12773 is a critical vulnerability in Realtek ADSL/PON Modem SoC, published on 8 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security misconfiguration vulnerability exists in the SDK of some Realtek ADSL/PON Modem SoC firmware, which allows attackers using a default password to execute arbitrary commands remotely via the build-in network monitoring tool.

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

It affects 1 product.


Products: Realtek Adsl Router Soc Firmware.

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

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

## Is CVE-2020-12773 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12773 is a critical vulnerability in Realtek ADSL/PON Modem SoC, published on 8 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-12773 in the wild and no public exploit code.

Affected product: Realtek ADSL/PON Modem SoC. 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-12773/ (Markdown: https://insights.sbomify.com/CVE-2020-12773/index.md)
```

## Sources

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

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