# CVE-2012-4443: Privilege escalation in n/a

> Local attackers can gain root privileges by exploiting CGI script execution running with root UID/GID in Monkey HTTP Daemon.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4ggc-896w-79rc

## What is CVE-2012-4443?

CVE-2012-4443 is a medium-severity vulnerability in n/a, published on 5 Oct 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Monkey HTTP Daemon 0.9.3 uses a real UID of root and a real GID of root during execution of CGI scripts, which might allow local users to gain privileges by leveraging cgi-bin write access.

Weakness: CWE-264

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

It affects 1 product.


Products: Monkey-Project Monkey.

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

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

## Is CVE-2012-4443 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2159](https://insights.sbomify.com/CVE-2013-2159/): Auth bypass in monkey (critical 9.8)
- [CVE-2025-63649](https://insights.sbomify.com/CVE-2025-63649/): Denial of service in n/a (high 7.5)
- [CVE-2025-63650](https://insights.sbomify.com/CVE-2025-63650/): Denial of service in n/a (high 7.5)
- [CVE-2025-63651](https://insights.sbomify.com/CVE-2025-63651/): Use after free in n/a (high 7.5)
- [CVE-2025-63652](https://insights.sbomify.com/CVE-2025-63652/): Use after free in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4443 is a medium-severity vulnerability in n/a, published on 5 Oct 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-4443 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-4443/ (Markdown: https://insights.sbomify.com/CVE-2012-4443/index.md)
```

## Sources

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

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