CVE-2012-3274
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 · uneditedStack-based buffer overflow in uam.exe in the User Access Manager (UAM) component in HP Intelligent Management Center (IMC) before 5.1 E0101P01 allows remote attackers to execute arbitrary code via vectors related to log data.
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 confidenceStack-based buffer overflow in the uam.exe component of HP Intelligent Management Center (IMC) allows remote attackers to execute arbitrary code by sending specially crafted log data to the User Access Manager service.
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<= 5.1= 5.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify HP IMC installationLocate HP Intelligent Management Center in installed programs or check for its installation directory (typically under HP or Hewlett-Packard in Program Files)Affected if HP IMC is installed on the system
-
Determine HP IMC versionCheck the version of HP Intelligent Management Center installed by reviewing the installed program details, About section in the application, or version information in the installation directoryAffected if The installed version is 5.0 or 5.1 (or any version <= 5.1)
-
Locate uam.exe componentSearch for the uam.exe file within the HP IMC installation directory, typically found in the bin or subdirectories of the IMC installation pathAffected if The uam.exe file exists in the HP IMC installation folder
-
Check User Access Manager service statusVerify if the User Access Manager service (uam.exe) is running on the system, either through Windows Services or process listAffected if The User Access Manager service (uam.exe) is currently running or enabled
The system is affected if HP Intelligent Management Center version 5.0 or 5.1 is installed with the uam.exe component present and the User Access Manager service enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade HP IMC to version 5.1 E0101P01 or later to patch the vulnerable uam.exe component.
5.1 E0101P01 or later
- Back up the HP Intelligent Management Center database and all configurations before starting the upgrade
- Download HP Intelligent Management Center version 5.1 E0101P01 or later from the official HP support portal (h20566.www2.hp.com)
- Stop all HP IMC services on the affected server, including the User Access Manager (UAM) component
- Run the installer for version 5.1 E0101P01 following HP's standard upgrade procedures
- After installation completes, restart all HP IMC services
- Verify the UAM component (uam.exe) is running correctly and accessible
- Confirm the vulnerability is remediated by checking that the affected uam.exe version no longer has the buffer overflow vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3274 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-3274 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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