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

> Unauthenticated attackers can bypass authorization to disclose sensitive information on D-Link DIR-859 routers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c2wf-4gpc-mpwc

## What is CVE-2019-20213?

CVE-2019-20213 is a high-severity authentication bypass vulnerability in n/a, published on 2 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DIR-859 routers before v1.07b03_beta allow Unauthenticated Information Disclosure via the AUTHORIZED_GROUP=1%0a value, as demonstrated by vpnconfig.php.

Weakness: CWE-863 (Incorrect Authorization), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 14 products.


Products: Dlink Dir-818lx Firmware, Dlink Dir-822 Firmware, Dlink Dir-823 Firmware, Dlink Dir-859 Firmware, Dlink Dir-865l Firmware, Dlink Dir-868l Firmware, Dlink Dir-869 Firmware, Dlink Dir-880l Firmware, Dlink Dir-885l Firmware, Dlink Dir-885r Firmware, Dlink Dir-890l Firmware, Dlink Dir-890r Firmware, Dlink Dir-895l Firmware, Dlink Dir-895r Firmware.

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

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

## Is CVE-2019-20213 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-17621](https://insights.sbomify.com/CVE-2019-17621/): D-Link DIR-859 Router Command Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-20213 is a high-severity authentication bypass vulnerability in n/a, published on 2 Jan 2020. 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-20213 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-20213/ (Markdown: https://insights.sbomify.com/CVE-2019-20213/index.md)
```

## Sources

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

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