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

> Remote attackers can obtain sensitive full pathname information via a crafted error message in PaperThin CommonSpot Content Server.

- **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:** 29 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vq47-f2jr-4vpm

## What is CVE-2005-4575?

CVE-2005-4575 is a medium-severity vulnerability in n/a, published on 29 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PaperThin CommonSpot Content Server 4.5 and earlier allow remote attackers to obtain sensitive information via an invalid errmsg parameter to loader.cfm with a url parameter set to email-login-info.cfm, which leaks the full pathname in the resulting error message.

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

It affects 1 product.


Products: Paperthin Commonspot Content Server.

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

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

## Is CVE-2005-4575 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2863](https://insights.sbomify.com/CVE-2014-2863/): Path traversal in n/a (critical 10.0)
- [CVE-2014-2864](https://insights.sbomify.com/CVE-2014-2864/): Path traversal in n/a (critical 10.0)
- [CVE-2014-2866](https://insights.sbomify.com/CVE-2014-2866/): Security feature bypass in n/a (critical 10.0)
- [CVE-2014-2867](https://insights.sbomify.com/CVE-2014-2867/): File upload in n/a (critical 10.0)
- [CVE-2014-2874](https://insights.sbomify.com/CVE-2014-2874/): Command injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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