# CVE-2004-0614: File upload in n/a

> Remote attackers can bypass file size restrictions in osTicket by manipulating hidden form fields, potentially causing denial of service.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jun 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-m3f7-q43h-937m

## What is CVE-2004-0614?

CVE-2004-0614 is a medium-severity vulnerability in n/a, published on 30 Jun 2004. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

osTicket trusts a hidden form field in the submit form to limit the upload size of a document, which could allow remote attackers to upload a file of any size.

## Which versions are affected by CVE-2004-0614?

It affects 1 product.


Products: Osticket Osticket Sts.

## How do I fix CVE-2004-0614?

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

## Is CVE-2004-0614 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2153](https://insights.sbomify.com/CVE-2005-2153/): SQL injection in n/a (high 7.5)
- [CVE-2005-2154](https://insights.sbomify.com/CVE-2005-2154/): Path traversal in n/a (high 7.5)
- [CVE-2004-0613](https://insights.sbomify.com/CVE-2004-0613/): File upload in n/a (high 7.5)
- [CVE-2006-6733](https://insights.sbomify.com/CVE-2006-6733/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0614 and fix it if it is affected.

What it is: CVE-2004-0614 is a medium-severity vulnerability in n/a, published on 30 Jun 2004. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2004-0614 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-2004-0614/ (Markdown: https://insights.sbomify.com/CVE-2004-0614/index.md)
```

## Sources

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

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