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

> Remote attackers can obtain sensitive information, including encrypted passwords, by directly requesting a specific file stored under the web document root.

- **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:** 25 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hww3-73x9-5836

## What is CVE-2006-0404?

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

### Official description

Note-A-Day Weblog 2.2 stores sensitive data under the web document root with insufficient access control, which allows remote attackers to obtain sensitive information via a direct request to archive/.phpass-admin, which contains encrypted passwords.

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

It affects 1 product.


Products: Mike Macgirvin Note-a-Day Weblog.

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

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

## Is CVE-2006-0404 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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