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

> Attackers can change the administrator password without knowing the current one, leading to full device takeover on D-Link DIR-601 routers.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** 4 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vh4j-9cjw-6wxg

## What is CVE-2018-10641?

CVE-2018-10641 is a high-severity authentication bypass vulnerability in n/a, published on 4 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DIR-601 A1 1.02NA devices do not require the old password for a password change, which occurs in cleartext.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Dlink Dir-601 Firmware.

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

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

## Is CVE-2018-10641 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16327](https://insights.sbomify.com/CVE-2019-16327/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-16326](https://insights.sbomify.com/CVE-2019-16326/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-12710](https://insights.sbomify.com/CVE-2018-12710/): Information disclosure in n/a (high 8.0)
- [CVE-2018-5708](https://insights.sbomify.com/CVE-2018-5708/): Information disclosure in n/a (high 8.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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