# CVE-2012-5520: Command injection in n/a

> Remote attackers can execute arbitrary commands on OpenVAS Manager by injecting malicious input into IP or port fields in OMP requests.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fqgh-fg9x-68q8

## What is CVE-2012-5520?

CVE-2012-5520 is a high-severity command injection vulnerability in n/a, published on 26 Nov 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The send_to_sourcefire function in manage_sql.c in OpenVAS Manager 3.x before 3.0.4 allows remote attackers to execute arbitrary commands via the (1) IP address or (2) port number field in an OMP request.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2012-5520?

It affects 1 product.


Products: Openvas Openvas Manager.

## How do I fix CVE-2012-5520?

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

## Is CVE-2012-5520 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-0018](https://insights.sbomify.com/CVE-2011-0018/): Command injection in n/a (critical 9.0)
- [CVE-2011-1597](https://insights.sbomify.com/CVE-2011-1597/): File upload in Manager (high 8.8)
- [CVE-2013-6765](https://insights.sbomify.com/CVE-2013-6765/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5520 and fix it if it is affected.

What it is: CVE-2012-5520 is a high-severity command injection vulnerability in n/a, published on 26 Nov 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-5520 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-2012-5520/ (Markdown: https://insights.sbomify.com/CVE-2012-5520/index.md)
```

## Sources

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

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