CVE-2012-3280
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 · uneditedMultiple unspecified vulnerabilities on HP NonStop Servers H06.x and J06.x allow remote authenticated users to obtain sensitive information, modify data, or cause a denial of service via an OSS Remote Operation over an Expand connection.
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 confidenceMultiple unspecified vulnerabilities in HP NonStop Servers H06.x and J06.x allow remote authenticated users to exploit OSS Remote Operation over an Expand connection to obtain sensitive information, modify data, or cause denial of 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= g06.29.00= g06.29.01= g06.29.02= g06.29.03= g06.30.00= g06.30.01= g06.30.02= g06.31.00= g06.31.01= g06.32.00= g06.32.01= h06.08.00all versionsCVSS 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
- Adjacent
- Complexity
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Complete
AV:A/AC:M/Au:S/C:P/I:P/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 NonStop Server installationLocate the NonStop Server system and retrieve its version information using system utilities or version display commandsAffected if The system is running HP NonStop Server software
-
Check NonStop Server version against affected rangesCompare the installed version number to the affected version list: g06.29.00 through h06.08.00, or any H06.x/J06.x releaseAffected if Version matches g06.29.00, g06.29.01, g06.29.02, g06.29.03, g06.30.00, g06.30.01, g06.30.02, g06.31.00, g06.31.01, g06.32.00, g06.32.01, h06.08.00, or falls within H06.x/J06.x branches
-
Verify OSS Remote Operation feature statusInspect the OSS Remote Operation configuration or subsystem status to determine if it is enabled on the systemAffected if OSS Remote Operation over Expand is actively configured or running
-
Inspect Expand network exposureReview network configuration, access controls, or Expand interface settings to determine if OSS Remote Operation is accessible over network connectionsAffected if Expand/OSS interfaces are exposed to network access beyond localhost or restricted administrative networks
System is affected if it runs HP NonStop Server with OSS Remote Operation enabled on versions H06.x or J06.x, or any version between g06.29.00 and h06.08.00, with accessible Expand network interfaces.
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.
From vendor dataContact HP for applicable patches or updates for NonStop Servers H06.x and J06.x; restrict network access to Expand/OSS interfaces to only necessary authenticated personnel and monitor for anomalous remote operation activity.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3280 — 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-3280 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