# CVE-2003-1409: Information disclosure in n/a

> Remote attackers can obtain sensitive directory path information by sending invalid HTTP parameters to TOPo web application scripts.

- **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:** 20 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-83mw-jhfh-84qc

## What is CVE-2003-1409?

CVE-2003-1409 is a medium-severity vulnerability in n/a, published on 20 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TOPo 1.43 allows remote attackers to obtain sensitive information by sending an HTTP request with an invalid parameter to (1) in.php or (2) out.php, which reveals the path to the TOPo directory in the error message.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2003-1409?

It affects 1 product.


Products: Ej3 Topo.

## How do I fix CVE-2003-1409?

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

## Is CVE-2003-1409 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1409 exists.

Public exploit code:

- TOPO 1.41 - Full Path Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-3536](https://insights.sbomify.com/CVE-2006-3536/): Code injection in n/a (high 7.5)
- [CVE-2006-3833](https://insights.sbomify.com/CVE-2006-3833/): Missing authorization in n/a (medium 5.0)
- [CVE-2006-3834](https://insights.sbomify.com/CVE-2006-3834/): Information disclosure in n/a (medium 5.0)
- [CVE-2005-1716](https://insights.sbomify.com/CVE-2005-1716/): Information disclosure in n/a (medium 5.0)
- [CVE-2006-0984](https://insights.sbomify.com/CVE-2006-0984/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1409 and fix it if it is affected.

What it is: CVE-2003-1409 is a medium-severity vulnerability in n/a, published on 20 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1409 exists.

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-2003-1409/ (Markdown: https://insights.sbomify.com/CVE-2003-1409/index.md)
```

## Sources

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

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