# CVE-2002-1810: Missing authorization in n/a

> Remote attackers can access the TFTP server without authentication to read sensitive configuration files containing administrative passwords and encryption keys.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 28 Jun 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-pq3h-q9vp-54r6

## What is CVE-2002-1810?

CVE-2002-1810 is a high-severity missing authorization vulnerability in n/a, published on 28 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DWL-900AP+ Access Point 2.1 and 2.2 allows remote attackers to access the TFTP server without authentication and read the config.img file, which contains sensitive information such as the administrative password, the WEP encryption keys, and network configuration information.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2002-1810?

It affects 1 product.


Products: Dlink Dwl-900ap\+ Firmware.

## How do I fix CVE-2002-1810?

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

## Is CVE-2002-1810 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1810 and fix it if it is affected.

What it is: CVE-2002-1810 is a high-severity missing authorization vulnerability in n/a, published on 28 Jun 2005. 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-2002-1810 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-2002-1810/ (Markdown: https://insights.sbomify.com/CVE-2002-1810/index.md)
```

## Sources

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

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