# CVE-2019-19825: Security feature bypass in n/a

> Attackers can bypass CAPTCHA protection on TOTOLINK routers to perform administrative actions via HTTP requests.

- **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:** 27 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qx9v-3w62-8wqf

## What is CVE-2019-19825?

CVE-2019-19825 is a critical vulnerability in n/a, published on 27 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On certain TOTOLINK Realtek SDK based routers, the CAPTCHA text can be retrieved via an {"topicurl":"setting/getSanvas"} POST to the boafrm/formLogin URI, leading to a CAPTCHA bypass. (Also, the CAPTCHA text is not needed once the attacker has determined valid credentials. The attacker can perform router actions via HTTP requests with Basic Authentication.) This affects A3002RU through 2.0.0, A702R through 2.1.3, N301RT through 2.1.6, N302R through 3.4.0, N300RT through 3.4.0, N200RE through 4.0.0, N150RT through 3.4.0, and N100RE through 3.4.0.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-19825?

It affects 8 products.


Products: Totolink A3002ru Firmware, Totolink A702r Firmware, Totolink N100re Firmware, Totolink N150rt Firmware, Totolink N200re Firmware, Totolink N300rt Firmware, Totolink N301rt Firmware, Totolink N302r Firmware.

## How do I fix CVE-2019-19825?

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

## Is CVE-2019-19825 being exploited?

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

Public exploit code:

- TOTOLINK/Realtek Routers - CAPTCHA Bypass (nuclei): http/cves/2019/CVE-2019-19825.yaml

## Other vulnerabilities in n/a

- [CVE-2024-34198](https://insights.sbomify.com/CVE-2024-34198/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-35491](https://insights.sbomify.com/CVE-2022-35491/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-13306](https://insights.sbomify.com/CVE-2018-13306/): Command injection in n/a (critical 9.8)
- [CVE-2018-13307](https://insights.sbomify.com/CVE-2018-13307/): Command injection in n/a (critical 9.8)
- [CVE-2018-13314](https://insights.sbomify.com/CVE-2018-13314/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19825 and fix it if it is affected.

What it is: CVE-2019-19825 is a critical vulnerability in n/a, published on 27 Jan 2020. 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-2019-19825 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-2019-19825/ (Markdown: https://insights.sbomify.com/CVE-2019-19825/index.md)
```

## Sources

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

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