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

> Authenticated users can determine file existence via the folder parameter in attachment.html when mailbox.dat is missing.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2ggv-947x-gfhx

## What is CVE-2005-1490?

CVE-2005-1490 is a low-severity vulnerability in n/a, published on 11 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Merak Mail Server 8.0.3 with Icewarp Web Mail 5.4.2, when the mailbox.dat file does not exist, allows remote authenticated users to determine if a file exists via the folder parameter to attachment.html.

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

It affects 2 products.


Products: Icewarp Web Mail, Merak Mail Server.

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

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

## Is CVE-2005-1490 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1670](https://insights.sbomify.com/CVE-2004-1670/): Path traversal in n/a (high 7.5)
- [CVE-2004-1672](https://insights.sbomify.com/CVE-2004-1672/): Missing authorization in n/a (high 7.5)
- [CVE-2004-1673](https://insights.sbomify.com/CVE-2004-1673/): File upload in n/a (high 7.5)
- [CVE-2004-1674](https://insights.sbomify.com/CVE-2004-1674/): Path traversal in n/a (high 7.5)
- [CVE-2002-0258](https://insights.sbomify.com/CVE-2002-0258/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1490 is a low-severity vulnerability in n/a, published on 11 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-1490 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-1490/ (Markdown: https://insights.sbomify.com/CVE-2005-1490/index.md)
```

## Sources

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

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