# CVE-2024-31810: Hardcoded credentials in n/a

> Attackers can gain root access to TOTOLINK EX200 routers using a hardcoded password found in the system files.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 13 May 2024
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-cc7f-xj8f-c4mm

## What is CVE-2024-31810?

CVE-2024-31810 is a critical vulnerability in n/a, published on 13 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TOTOLINK EX200 V4.0.3c.7646_B20201211 was discovered to contain a hardcoded password for root at /etc/shadow.sample.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2024-31810?

It affects 1 product.


Products: Totolink Ex200 Firmware.

## How do I fix CVE-2024-31810?

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

## Is CVE-2024-31810 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31810 exists.

## Other vulnerabilities in n/a

- [CVE-2024-31807](https://insights.sbomify.com/CVE-2024-31807/): Code injection in n/a (critical 9.8)
- [CVE-2021-43711](https://insights.sbomify.com/CVE-2021-43711/): Command injection in n/a (critical 9.8)
- [CVE-2024-31815](https://insights.sbomify.com/CVE-2024-31815/): Missing authorization in n/a (critical 9.1)
- [CVE-2024-31808](https://insights.sbomify.com/CVE-2024-31808/): Command injection in n/a (high 8.8)
- [CVE-2024-31809](https://insights.sbomify.com/CVE-2024-31809/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-31810 and fix it if it is affected.

What it is: CVE-2024-31810 is a critical vulnerability in n/a, published on 13 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31810 exists.

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-2024-31810/ (Markdown: https://insights.sbomify.com/CVE-2024-31810/index.md)
```

## Sources

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

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