# CVE-2018-17777: Auth bypass in n/a

> Attackers can bypass login and gain admin access if the default Parental Control PIN is used, allowing full router control.

- **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:** 18 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r292-8vw9-293g

## What is CVE-2018-17777?

CVE-2018-17777 is a critical authentication bypass vulnerability in n/a, published on 18 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on D-Link DVA-5592 A1_WI_20180823 devices. If the PIN of the page "/ui/cbpc/login" is the default Parental Control PIN (0000), it is possible to bypass the login form by editing the path of the cookie "sid" generated by the page. The attacker will have access to the router control panel with administrator privileges.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-17777?

It affects 1 product.


Products: Dlink Dva-5592 Firmware.

## How do I fix CVE-2018-17777?

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

## Is CVE-2018-17777 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-6969](https://insights.sbomify.com/CVE-2019-6969/): Auth bypass in n/a (high 7.5)
- [CVE-2019-6968](https://insights.sbomify.com/CVE-2019-6968/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17777 and fix it if it is affected.

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

## Sources

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

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