dbcve.org
OpenvmsOperating system · Hp

CVE-2012-2010

MEDIUM · 6.9 CVSS v2.0 Published 2012-05-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
The ACMELOGIN implementation in HP OpenVMS 8.3 and 8.4 on the Alpha platform, and 8.3, 8.3-1H1, and 8.4 on the Itanium platform, when the SYS$ACM system service is enabled, allows local users to gain privileges via unspecified vectors.

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

Local privilege escalation vulnerability in HP OpenVMS ACMELOGIN implementation when the SYS$ACM system service is enabled. Allows local users to gain elevated privileges through unspecified vectors on affected Alpha and Itanium platform versions.

MitigationDisable the SYS$ACM system service if not required, or apply HP patches for the affected OpenVMS versions. Limit local access to trusted users only.

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
OpenvmsOperating system
Affected:= 8.3= 8.3-1h1= 8.4

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
Local
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:M/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 OpenVMS version
    Use the SHOW VERSION command or check system documentation to determine the installed OpenVMS version number
    Affected if The version is 8.3, 8.3-1h1, or 8.4 on Alpha or Itanium platforms
  2. Confirm system architecture
    Verify the system runs on Alpha or Itanium hardware architecture using SHOW CPU or similar system information command
    Affected if Running on affected Alpha or Itanium platform architectures
  3. Check if SYS$ACM system service is enabled
    Inspect system service configuration or use commands to query whether the SYS$ACM system service is active and enabled on the system
    Affected if SYS$ACM system service is enabled and running
  4. Verify ACMELOGIN is configured
    Check if the ACMELOGIN authentication mechanism is configured or in use on the system by reviewing login configuration files or system settings
    Affected if ACMELOGIN is implemented or configured as the authentication method

The environment is affected if running OpenVMS version 8.3, 8.3-1h1, or 8.4 on Alpha or Itanium with the SYS$ACM system service enabled and ACMELOGIN in use

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the SYS$ACM system service if not required, or apply HP patches for the affected OpenVMS versions. Limit local access to trusted users only.

Fix this in Openvms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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