# CVE-2005-4520: Other in n/a

> Unspecified port injection vulnerabilities in Mantis filters allow attackers to potentially compromise the application, requiring an upgrade to a patched version.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 28 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pv7q-p55j-x95w

## What is CVE-2005-4520?

CVE-2005-4520 is a medium-severity vulnerability in n/a, published on 28 Dec 2005. It can be exploited over the network.

### Official description

Unspecified "port injection" vulnerabilities in filters in Mantis 1.0.0rc3 and earlier have unknown impact and attack vectors.  NOTE: due to a lack of relevant details in the vendor changelog, which is the source of this description, it is unclear whether this is a duplicate of another CVE.

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

It affects 1 product.


Products: Mantis Mantis.

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

Upgrade to a fixed version.

## Is CVE-2005-4520 being exploited?

There is no known exploitation of CVE-2005-4520 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-4520 and fix it if it is affected.

What it is: CVE-2005-4520 is a medium-severity vulnerability in n/a, published on 28 Dec 2005. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2005-4520 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-4520/ (Markdown: https://insights.sbomify.com/CVE-2005-4520/index.md)
```

## Sources

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

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