CVE-2012-0697
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 · uneditedHP StorageWorks P2000 G3 MSA array systems have a default account, which makes it easier for remote attackers to perform administrative tasks via unspecified vectors, a different vulnerability than CVE-2011-4788.
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 confidenceHP StorageWorks P2000 G3 MSA array systems contain a hardcoded default administrative account with predictable credentials. This allows unauthenticated remote attackers to gain full administrative access to the storage array via network vectors, enabling them to modify configuration, access stored data, or disrupt storage services.
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 dataall 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
- 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 the storage array modelAccess the storage array management interface or check system documentation/inventory to confirm the device is an HP StorageWorks P2000 G3 MSA array systemAffected if The device is confirmed to be an HP StorageWorks P2000 G3 MSA model
-
Verify default administrative account statusLog into the P2000 G3 management interface and navigate to user account management. Check if the default administrative user account (the hardcoded account referenced in this CVE) exists and is enabledAffected if The default administrative account is present and enabled on the system
-
Confirm default credentials are unchangedAttempt to authenticate using the known default credentials associated with this CVE (the hardcoded predictable credentials). If authentication succeeds, the credentials have not been changedAffected if Default credentials still work and have not been modified from the vendor defaults
-
Assess network accessibility of management interfaceDetermine if the P2000 G3 management interface (typically accessible via HTTP/HTTPS on network ports) is exposed to untrusted networks or the internet. Check firewall rules and network segmentation around the storage arrayAffected if The management interface is accessible from untrusted network segments or directly from the internet
A user is affected if they operate an HP StorageWorks P2000 G3 MSA system where the hardcoded default administrative account remains enabled with unchanged credentials and the management interface is network-accessible to potential attackers.
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 dataImmediately change or disable the default account credentials on affected P2000 G3 MSA systems. Implement network segmentation to restrict management interface access to authorized administrative hosts only.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0697 — 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-0697 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