Loading vulnerability…
A stack-based buffer overflow vulnerability exists in uam.exe, part of the User Access Manager (UAM) component in HP Intelligent Management Center (IMC) versions prior to 5.1 E0101P01. The vulnerability is triggered by improper handling of log data, allowing remote attackers to overflow a stack buffer and potentially execute arbitrary code on the affected system.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (hp_imc_uam.rb) that exploits a remote buffer overflow vulnerability (CVE-2012-3274) in the HP Intelligent Management Center (iMC) UAM component (versions 5.0 E0101 and 5.0 E0102) running on Windows Server 2003 SP2. The exploit targets the uam.exe service, which listens on UDP port 1811, by sending a specially crafted UDP packet that triggers a buffer overflow via insecure use of the 'sprint' function for logging. The module includes a ROP chain to bypass DEP and allows the attacker to execute arbitrary code with elevated privileges. The payload is customizable using Metasploit's payload system. The repository is structured as a typical Metasploit exploit module, with all logic contained in a single Ruby file. No additional endpoints or files are present.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.