# CVE-2007-2197: Race condition in n/a

> Remote attackers can obtain other clients' HTTP responses via a race condition in the NeatUpload ASP.NET component.

- **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:** 24 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-64j7-8j49-mhvq

## What is CVE-2007-2197?

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

### Official description

Race condition in the NeatUpload ASP.NET component 1.2.11 through 1.2.16, 1.1.18 through 1.1.23, and trunk.379 through trunk.445 allows remote attackers to obtain other clients' HTTP responses via multiple simultaneous requests, which triggers multiple calls to HttpWorkerRequest.FlushResponse for the same HttpWorkerRequest object and causes a buffer to be reused for a different request.

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

It affects 1 product.


Products: Brettle Development Neatupload.

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

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

## Is CVE-2007-2197 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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