# CVE-2007-6349: Denial of service in n/a

> Remote attackers can cause denial of service via CPU consumption in Perforce P4Web by sending HTTP requests with empty bodies and positive Content-Length headers.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4fr6-rgq9-hcp4

## What is CVE-2007-6349?

CVE-2007-6349 is a high-severity denial of service vulnerability in n/a, published on 20 Dec 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

P4Webs.exe in Perforce P4Web 2006.2 and earlier, when running on Windows, allows remote attackers to cause a denial of service (CPU consumption) via an HTTP request with an empty body and a Content-Length greater than 0.

Weakness: CWE-399

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

It affects 1 product.


Products: Perforce P4web.

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

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

## Is CVE-2007-6349 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-1410](https://insights.sbomify.com/CVE-2013-1410/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6349 is a high-severity denial of service vulnerability in n/a, published on 20 Dec 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-6349 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-6349/ (Markdown: https://insights.sbomify.com/CVE-2007-6349/index.md)
```

## Sources

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

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