# CVE-2002-1082: Path traversal in n/a

> Remote attackers can manipulate local files via the image upload feature in ezContents, requiring low privileges.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-x8fj-pqgj-8m55

## What is CVE-2002-1082?

CVE-2002-1082 is a medium-severity path traversal vulnerability in n/a, published on 31 Aug 2002. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Image Upload capability for ezContents 1.40 and earlier allows remote attackers to cause ezContents to perform operations on local files as if they were uploaded.

## Which versions are affected by CVE-2002-1082?

It affects 1 product.


Products: Visualshapers Ezcontents.

## How do I fix CVE-2002-1082?

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

## Is CVE-2002-1082 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-2135](https://insights.sbomify.com/CVE-2008-2135/): SQL injection in n/a (high 7.5)
- [CVE-2006-4477](https://insights.sbomify.com/CVE-2006-4477/): Code injection in n/a (high 7.5)
- [CVE-2006-4478](https://insights.sbomify.com/CVE-2006-4478/): SQL injection in n/a (high 7.5)
- [CVE-2003-1214](https://insights.sbomify.com/CVE-2003-1214/): Auth bypass in n/a (high 7.5)
- [CVE-2004-0070](https://insights.sbomify.com/CVE-2004-0070/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1082 and fix it if it is affected.

What it is: CVE-2002-1082 is a medium-severity path traversal vulnerability in n/a, published on 31 Aug 2002. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1082 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-2002-1082/ (Markdown: https://insights.sbomify.com/CVE-2002-1082/index.md)
```

## Sources

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

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