# CVE-2019-19743: Privilege escalation in n/a

> A normal user can create a root administrator account on D-Link DIR-615 routers, leading to full device compromise.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** 16 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jrp5-23hf-jfg7

## What is CVE-2019-19743?

CVE-2019-19743 is a medium-severity vulnerability in n/a, published on 16 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On D-Link DIR-615 devices, a normal user is able to create a root(admin) user from the D-Link portal.

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

It affects 1 product.


Products: Dlink Dir-615 T1 Firmware.

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

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

## Is CVE-2019-19743 being exploited?

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

Public exploit code:

- D-Link DIR-615 - Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19743 is a medium-severity vulnerability in n/a, published on 16 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19743 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-19743/ (Markdown: https://insights.sbomify.com/CVE-2019-19743/index.md)
```

## Sources

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

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