# CVE-2012-3448: Code injection in n/a

> Remote attackers can execute arbitrary PHP code in Ganglia Web, posing a critical risk to monitoring infrastructure.

- **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:** 6 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-3448, DSA-2610-1, GHSA-qv5c-fqrv-r4vp

## What is CVE-2012-3448?

CVE-2012-3448 is a high-severity code injection vulnerability in n/a, published on 6 Aug 2012. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in Ganglia Web before 3.5.1 allows remote attackers to execute arbitrary PHP code via unknown attack vectors.

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

It affects 1 product.


Products: Ganglia Ganglia-Web.

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

Upgrade to a fixed version.

## Is CVE-2012-3448 being exploited?

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

Public exploit code:

- Ganglia Web Frontend < 3.5.1 - PHP Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2024-52762](https://insights.sbomify.com/CVE-2024-52762/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-52763](https://insights.sbomify.com/CVE-2024-52763/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-20378](https://insights.sbomify.com/CVE-2019-20378/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-20379](https://insights.sbomify.com/CVE-2019-20379/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2013-1770](https://insights.sbomify.com/CVE-2013-1770/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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