dbcve.org
Operations AgentApplication · Hp

CVE-2012-2020

HIGH · 10.0 CVSS v2.0 Published 2012-07-11
Fix available
A fix is available. Upgrade to after 11.0 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
Unspecified vulnerability in HP Operations Agent before 11.03.12 allows remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-1326.

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 · moderate confidence

HP Operations Agent before version 11.03.12 contains an unspecified vulnerability (ZDI-CAN-1326) allowing remote attackers to execute arbitrary code via unknown vectors. The CVSS 10 score indicates network-exploitable, no-authentication-required attack with complete impact on confidentiality, integrity, and availability.

MitigationUpgrade HP Operations Agent to version 11.03.12 or later to remediate this vulnerability.

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
Operations AgentApplication
Affected:<= 11.0= 7.36= 8.51= 8.51.102= 8.52= 8.53= 8.60= 8.60.005= 8.60.006= 8.60.007= 8.60.7= 8.60.008

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. Confirm HP Operations Agent is installed
    Look for the HP Operations Agent installation directory (typically under C:\Program Files\HP\ or C:\HP\), check Windows Registry under HKLM\SOFTWARE\HP\HP Operations Agent, or check for running processes named opcagt.exe, ovbb, or ovcd
    Affected if HP Operations Agent software is found on the system
  2. Identify the installed version
    Run the command 'opcagt -version' or 'opcagt -v' from the bin directory, check the version in the registry key HKLM\SOFTWARE\HP\HP Operations Agent\CurrentVersion, or examine a version.txt file in the installation directory
    Affected if The version returned is 7.36, 8.51, 8.51.102, 8.52, 8.53, 8.60, 8.60.005, 8.60.006, 8.60.007, 8.60.7, 8.60.008, or any version <= 11.0 prior to 11.03.12
  3. Verify the CVE-specific component is active
    Confirm the HP Operations Agent core services (opcagt, ovbb, ovcd) are running and the HP Operations Manager components are enabled. Check if port 383 (default OPC agent port) is listening
    Affected if The agent services are active and the vulnerability can be exploited over the network

If HP Operations Agent is installed and the version is 11.03.11 or lower (including 7.36 through 8.60.008 and <= 11.0), the system is affected by CVE-2012-2020.

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
Upgrade available Upgrade to a release after 11.0
Interim mitigation

Upgrade HP Operations Agent to version 11.03.12 or later to remediate this vulnerability.

Recommended fix Moderate confidence

HP Operations Agent 11.03.12 or later

  1. 1. Identify the current version of HP Operations Agent installed by checking the software version through the HP Operations Agent management interface or command line tools.
  2. 2. Verify that the installed version is one of the affected versions: 7.36, 8.51, 8.51.102, or any version <= 11.0.
  3. 3. Obtain HP Operations Agent version 11.03.12 or later from the official HP/HPE software repository or support portal.
  4. 4. Follow HP's standard upgrade procedure for Operations Agent, which typically involves stopping the Operations Agent services, running the installer for the new version, and restarting services.
  5. 5. After upgrade, verify the new version is correctly installed and the services are running properly.
  6. 6. Confirm the vulnerability is remediated by verifying the installed version is 11.03.12 or higher.
Caveat Review HP upgrade documentation for any specific migration requirements or compatibility considerations when upgrading from older versions like 7.36 or 8.51

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

Fix this in Operations Agent Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-2020 — 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-2020 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