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

> Remote attackers can execute arbitrary Perl code via crafted requests in NetIQ Privileged User Manager, requiring immediate patching.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-5x6j-mfj4-3fc4

## What is CVE-2012-5932?

CVE-2012-5932 is a critical code injection vulnerability in n/a, published on 24 Dec 2012. It can be exploited over the network, with no action from the victim.

### Official description

Eval injection vulnerability in the ldapagnt_eval function in ldapagnt.dll in unifid.exe in NetIQ Privileged User Manager 2.3.x before 2.3.1 HF2 allows remote attackers to execute arbitrary Perl code via a crafted application/x-amf request.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Microfocus Privileged User Manager.

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

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

## Is CVE-2012-5932 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-5932 exists.

Public exploit code:

- NetIQ Privileged User Manager 2.3.1 ldapagnt_eval() Remote Perl Code Execution (metasploit)
- NetIQ Privileged User Manager 2.3.1 - 'ldapagnt_eval()' Perl Remote Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-5930](https://insights.sbomify.com/CVE-2012-5930/): Auth bypass in n/a (medium 6.4)
- [CVE-2012-5931](https://insights.sbomify.com/CVE-2012-5931/): Path traversal in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-5932 is a critical code injection vulnerability in n/a, published on 24 Dec 2012. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-5932 exists.

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-5932/ (Markdown: https://insights.sbomify.com/CVE-2012-5932/index.md)
```

## Sources

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

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