# CVE-2002-1038: File upload in n/a

> Remote attackers can manipulate arbitrary files via improper upload verification in Double Choco Latte, potentially leading to code execution or data modification.

- **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-vpxr-gggm-p35f

## What is CVE-2002-1038?

CVE-2002-1038 is a medium-severity 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

Double Choco Latte (DCL) before 20020706 does not properly verify if a file was uploaded, which allows remote attackers to conduct certain operations on arbitrary files via the (1) Projects: Upload File Attachment or (2) Work Orders: Import features.

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

It affects 1 product.


Products: Michael Dean Double Choco Latte.

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

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

## Is CVE-2002-1038 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-0887](https://insights.sbomify.com/CVE-2005-0887/): Code injection in n/a (high 7.5)
- [CVE-2002-1039](https://insights.sbomify.com/CVE-2002-1039/): Path traversal in n/a (medium 5.0)
- [CVE-2002-1037](https://insights.sbomify.com/CVE-2002-1037/): Cross-site scripting in n/a (medium 5.0)
- [CVE-2005-0888](https://insights.sbomify.com/CVE-2005-0888/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1038 is a medium-severity 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-1038 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-1038/ (Markdown: https://insights.sbomify.com/CVE-2002-1038/index.md)
```

## Sources

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

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