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

> Remote attackers can obtain the full script path via a divide-by-zero error in calculate.php, exposing sensitive file system information.

- **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:** 27 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5f29-m59c-2qhp

## What is CVE-2006-5896?

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

### Official description

REMLAB Web Mech Designer 2.0.5 allows remote attackers to obtain the full path of the script via an incorrect Tonnage parameter to calculate.php that triggers a divide-by-zero error, which leaks the path in an error message.

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

It affects 1 product.


Products: Remlab Web Mech Designer.

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

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

## Is CVE-2006-5896 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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