# CVE-2005-2149: SQL injection in n/a

> Remote attackers can exploit a configuration flaw to bypass security checks and perform SQL injection, leading to privilege escalation and data access.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/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:** 6 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2149, GHSA-r2fr-8m3m-rwqg

## What is CVE-2005-2149?

CVE-2005-2149 is a critical SQL injection vulnerability in n/a, published on 6 Jul 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

config.php in Cacti 0.8.6e and earlier allows remote attackers to set the no_http_headers switch, then modify session information to gain privileges and disable the use of addslashes to conduct SQL injection attacks.

## Which versions are affected by CVE-2005-2149?

It affects 1 product.


Products: The Cacti Group Cacti.

## How do I fix CVE-2005-2149?

Upgrade to a fixed version.

## Is CVE-2005-2149 being exploited?

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

## Other vulnerabilities in n/a

- [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)
- [CVE-2005-1525](https://insights.sbomify.com/CVE-2005-1525/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2149 and fix it if it is affected.

What it is: CVE-2005-2149 is a critical SQL injection vulnerability in n/a, published on 6 Jul 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2149 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-2005-2149/ (Markdown: https://insights.sbomify.com/CVE-2005-2149/index.md)
```

## Sources

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

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