# CVE-2005-1828: Information disclosure in n/a

> Remote attackers can obtain sensitive credentials stored in cleartext within the router configuration file.

- **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:** 2 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x7hf-rfv2-7qqq

## What is CVE-2005-1828?

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

### Official description

D-Link DSL-504T stores usernames and passwords in cleartext in the router configuration file, which allows remote attackers to obtain sensitive information.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2005-1828?

It affects 1 product.


Products: Dlink Dsl-504t Firmware.

## How do I fix CVE-2005-1828?

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

## Is CVE-2005-1828 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1827](https://insights.sbomify.com/CVE-2005-1827/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1828 and fix it if it is affected.

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

## Sources

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

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