# CVE-2006-5901: Hardcoded credentials in n/a

> Hardcoded DNS server IP in Hawking router allows remote attackers to cause denial of service or hijack the device by spoofing the server.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fc87-w9vj-xf39

## What is CVE-2006-5901?

CVE-2006-5901 is a medium-severity vulnerability in n/a, published on 15 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hawking Technology wireless router WR254-CA uses a hardcoded IP address among the set of DNS server IP addresses, which could allow remote attackers to cause a denial of service or hijack the router by attacking or spoofing the server at the hardcoded address.  NOTE: it could be argued that this issue reflects an inherent limitation of DNS itself, so perhaps it should not be included in CVE.

## Which versions are affected by CVE-2006-5901?

It affects 1 product.


Products: Hawking Technology Wr254-Ca Wireless Router.

## How do I fix CVE-2006-5901?

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

## Is CVE-2006-5901 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-5901 and fix it if it is affected.

What it is: CVE-2006-5901 is a medium-severity vulnerability in n/a, published on 15 Nov 2006. 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-2006-5901 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-2006-5901/ (Markdown: https://insights.sbomify.com/CVE-2006-5901/index.md)
```

## Sources

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

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