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

> Authenticated users can cause denial of service via CPU exhaustion by submitting large graph dimension parameters in Cacti.

- **Severity:** Medium 6.8 (`AV:N/AC:L/Au:S/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-3113, GHSA-36fx-rf6c-vc8x

## What is CVE-2007-3113?

CVE-2007-3113 is a medium-severity denial of service vulnerability in n/a, published on 7 Jun 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cacti 0.8.6i, and possibly other versions, allows remote authenticated users to cause a denial of service (CPU consumption) via a large value of the (1) graph_height or (2) graph_width parameter, different vectors than CVE-2007-3112.

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

It affects 1 product.


Products: The Cacti Group Cacti.

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

Upgrade to a fixed version.

## Is CVE-2007-3113 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2149](https://insights.sbomify.com/CVE-2005-2149/): SQL injection in n/a (critical 10.0)
- [CVE-2002-1478](https://insights.sbomify.com/CVE-2002-1478/): Command injection in n/a (critical 10.0)
- [CVE-2007-3112](https://insights.sbomify.com/CVE-2007-3112/): Denial of service in n/a (high 7.8)
- [CVE-2006-6799](https://insights.sbomify.com/CVE-2006-6799/): SQL injection in n/a (high 7.5)
- [CVE-2005-2148](https://insights.sbomify.com/CVE-2005-2148/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3113 is a medium-severity denial of service vulnerability in n/a, published on 7 Jun 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-3113 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-3113/ (Markdown: https://insights.sbomify.com/CVE-2007-3113/index.md)
```

## Sources

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

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