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

> Remote attackers can execute arbitrary SQL commands in Mantis, potentially compromising database integrity and confidentiality.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fvxj-gh8q-cx84

## What is CVE-2005-3336?

CVE-2005-3336 is a high-severity SQL injection vulnerability in n/a, published on 27 Oct 2005. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in Mantis 1.0.0RC2 and 0.19.2 allows remote attackers to execute arbitrary SQL commands via unknown vectors.

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

It affects 1 product.


Products: Mantis Mantis.

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

Upgrade to a fixed version.

## Is CVE-2005-3336 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6515](https://insights.sbomify.com/CVE-2006-6515/): Missing authorization in n/a (critical 10.0)
- [CVE-2006-0665](https://insights.sbomify.com/CVE-2006-0665/): Other in n/a (critical 10.0)
- [CVE-2002-1110](https://insights.sbomify.com/CVE-2002-1110/): SQL injection in n/a (critical 10.0)
- [CVE-2008-4687](https://insights.sbomify.com/CVE-2008-4687/): Code injection in n/a (critical 9.0)
- [CVE-2008-4689](https://insights.sbomify.com/CVE-2008-4689/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3336 is a high-severity SQL injection vulnerability in n/a, published on 27 Oct 2005. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3336 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-3336/ (Markdown: https://insights.sbomify.com/CVE-2005-3336/index.md)
```

## Sources

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

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