dbcve.org
Privileged User ManagerApplication · Microfocus

CVE-2012-5932

HIGH · 10.0 CVSS v2.0 Published 2012-12-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Eval injection vulnerability in the ldapagnt_eval function in ldapagnt.dll within unifid.exe in NetIQ Privileged User Manager 2.3.x allows remote attackers to execute arbitrary Perl code via crafted application/x-amf (Action Message Format) requests.

MitigationApply vendor hotfix 2.3.1 HF2 or later to patch the eval injection flaw; until patched, restrict network access to the unifid.exe service and consider disabling AMF endpoint exposure if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Privileged User ManagerApplication
Affected:= 2.3.0= 2.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Privileged User Manager is installed
    Locate the installation directory for NetIQ or Microfocus Privileged User Manager, typically found in C:\Novell\NAM\pwm or similar paths, and identify the product name and version.
    Affected if The product installed is NetIQ or Microfocus Privileged User Manager version 2.3.0 or 2.3.1
  2. Verify unifid.exe service is running
    Open Windows Services or use 'sc query' command to check if the unifid.exe service is running. This service hosts the vulnerable ldapagnt.dll component.
    Affected if The unifid.exe service is running and the ldapagnt.dll component is loaded
  3. Check installed product version
    Check the version of the Privileged User Manager installation by examining the unifid.exe file properties or checking the installed programs list in Control Panel.
    Affected if The installed version is exactly 2.3.0 or 2.3.1 (the affected versions)
  4. Determine if AMF endpoint is exposed
    Test if the server accepts application/x-amf content type requests on the unifid service ports (typically 8080 or 8443). Send an HTTP request with Content-Type: application/x-amf to the AMF endpoint.
    Affected if The AMF endpoint is accessible and responds to application/x-amf requests, allowing the eval injection attack surface to be reachable

If Privileged User Manager version 2.3.0 or 2.3.1 is installed with the unifid.exe service running and the AMF endpoint is exposed to the network, the environment is affected by CVE-2012-5932.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor hotfix 2.3.1 HF2 or later to patch the eval injection flaw; until patched, restrict network access to the unifid.exe service and consider disabling AMF endpoint exposure if not required.

Recommended fix High confidence

NetIQ Privileged User Manager 2.3.1 HF2 (HotFix 2) or latest 2.3.1.x stable release

  1. 1. Identify the current installed version of NetIQ Privileged User Manager (should be 2.3.0 or 2.3.1).
  2. 2. Navigate to the NetIQ download portal at www.netiq.com or download.novell.com.
  3. 3. Locate and download NetIQ Privileged User Manager version 2.3.1 HF2 (HotFix 2) or the latest available 2.3.1.x patch.
  4. 4. Review the hotfix release notes for any prerequisites or special installation instructions.
  5. 5. Apply the hotfix following NetIQ's standard patch deployment procedures for the unifid.exe component.
  6. 6. Verify the ldapagnt.dll version matches the patched release after installation.
  7. 7. Test the application/x-amf request handling to confirm the eval injection vulnerability is remediated.
  8. 8. Monitor for any application errors following the patch deployment.
Caveat Ensure compatibility testing is performed with other NetIQ components that integrate with Privileged User Manager before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Privileged User Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,104.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-5932 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-5932 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data