# CVE-2004-1990: Information disclosure in n/a

> Remote attackers can obtain sensitive path and user information from Aldo's Web Server by sending arbitrary characters in requests.

- **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:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-8c59-r54h-654w

## What is CVE-2004-1990?

CVE-2004-1990 is a medium-severity vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Aldo's Web Server (aweb) 1.5 allows remote attackers to gain sensitive information via an arbitrary character, which reveals the full path and the user running the aweb process, possibly due to a malformed request.

## Which versions are affected by CVE-2004-1990?

It affects 1 product.


Products: Aldo Vargas Aldos Web Server.

## How do I fix CVE-2004-1990?

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

## Is CVE-2004-1990 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1990 and fix it if it is affected.

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

## Sources

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

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