# CVE-2006-2901: Information disclosure in n/a

> Remote attackers can obtain sensitive system information, including passwords, by requesting arbitrary configuration files from the D-Link DWL-2100ap web server.

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

## What is CVE-2006-2901?

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

### Official description

The web server for D-Link Wireless Access-Point (DWL-2100ap) firmware 2.10na and earlier allows remote attackers to obtain sensitive system information via a request to an arbitrary .cfg file, which returns configuration information including passwords.

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

It affects 1 product.


Products: D-Link Dwl-2100ap.

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

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

## Is CVE-2006-2901 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2901 exists.

Public exploit code:

- D-Link DWL Series Access-Point 2.10na - Config Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2901 is a medium-severity vulnerability in n/a, published on 7 Jun 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2901 exists.

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-2901/ (Markdown: https://insights.sbomify.com/CVE-2006-2901/index.md)
```

## Sources

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

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