# CVE-2018-18009: Hardcoded credentials in n/a

> Remote attackers can discover admin credentials via dirary0.js on D-Link DIR-140L and DIR-640L routers, leading to unauthorized access.

- **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:** 21 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-849p-98gq-v4r9

## What is CVE-2018-18009?

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

### Official description

dirary0.js on D-Link DIR-140L, DIR-640L devices allows remote unauthenticated attackers to discover admin credentials.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 2 products.


Products: Dlink Dir-140l Firmware, Dlink Dir-640l Firmware.

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

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

## Is CVE-2018-18009 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18008](https://insights.sbomify.com/CVE-2018-18008/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-10824](https://insights.sbomify.com/CVE-2018-10824/): Information disclosure in n/a (critical 9.8)
- [CVE-2018-10822](https://insights.sbomify.com/CVE-2018-10822/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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