# CVE-2007-4385: Security feature bypass in n/a

> Remote attackers can bypass input validation in OWASP Stinger by using multipart requests, potentially exposing underlying application vulnerabilities.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fp6x-72cw-rg73

## What is CVE-2007-4385?

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

### Official description

OWASP Stinger before 2.5 allows remote attackers to bypass input validation routines by using multipart encoded requests instead of form-urlencoded requests.  NOTE: this might be used to expose vulnerabilities in applications that would otherwise be protected by the validation routines.

## Which versions are affected by CVE-2007-4385?

It affects 1 product.


Products: Owasp Stinger.

## How do I fix CVE-2007-4385?

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

## Is CVE-2007-4385 being exploited?

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

Public exploit code:

- OWASP Stinger - Filter Bypass (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4385 and fix it if it is affected.

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

## Sources

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

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