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

> Remote attackers can obtain the installation path via an invalid database parameter, leaking sensitive path information in error messages.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 25 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vcv8-85jr-j5m9

## What is CVE-2003-1517?

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

### Official description

cart.pl in Dansie shopping cart allows remote attackers to obtain the installation path via an invalid db parameter, which leaks the path in an error message.

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

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

It affects 1 product.


Products: Dansie Shopping Cart.

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

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

## Is CVE-2003-1517 being exploited?

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

Public exploit code:

- Dansie Shopping Cart - Server Error Message Installation Full Path Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-1243](https://insights.sbomify.com/CVE-2000-1243/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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