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

> Remote attackers can obtain sensitive mail directory paths via the login form, exposing internal server structure.

- **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:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6hfq-cp5h-927v

## What is CVE-2004-0336?

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

### Official description

LAN SUITE Web Mail 602Pro allows remote attackers to gain sensitive information via the mail login form, which contains the path to the mail directory.

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

It affects 1 product.


Products: Software602 602pro Lan Suite.

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

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

## Is CVE-2004-0336 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2152](https://insights.sbomify.com/CVE-2002-2152/): Missing authorization in n/a (critical 10.0)
- [CVE-2007-3203](https://insights.sbomify.com/CVE-2007-3203/): Memory corruption in n/a (high 7.5)
- [CVE-2001-0447](https://insights.sbomify.com/CVE-2001-0447/): Command injection in n/a (high 7.5)
- [CVE-2000-1115](https://insights.sbomify.com/CVE-2000-1115/): Memory corruption in n/a (high 7.5)
- [CVE-2004-0337](https://insights.sbomify.com/CVE-2004-0337/): Cross-site scripting in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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