# CVE-2019-6971: Auth bypass in n/a

> An attacker can bypass authentication on TP-Link TL-WR1043ND V2 routers by sending a crafted cookie, gaining full control of the device.

- **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:** 19 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4ccq-6mpg-3gmq

## What is CVE-2019-6971?

CVE-2019-6971 is a critical authentication bypass vulnerability in n/a, published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on TP-Link TL-WR1043ND V2 devices. An attacker can send a cookie in an HTTP authentication packet to the router management web interface, and fully control the router without knowledge of the credentials.

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

It affects 1 product.


Products: Tp-Link Tl-Wr1043nd Firmware.

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

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

## Is CVE-2019-6971 being exploited?

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

Public exploit code:

- TP-Link TL-WR1043ND 2 - Authentication Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-2646](https://insights.sbomify.com/CVE-2013-2646/): Denial of service in n/a (high 7.5)
- [CVE-2019-6972](https://insights.sbomify.com/CVE-2019-6972/): Weak cryptography in n/a (high 7.5)
- [CVE-2018-16119](https://insights.sbomify.com/CVE-2018-16119/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6971 is a critical authentication bypass vulnerability in n/a, published on 19 Jun 2019. 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-2019-6971 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-2019-6971/ (Markdown: https://insights.sbomify.com/CVE-2019-6971/index.md)
```

## Sources

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

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