CVE-2010-4115
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 Modular Smart Array P2000 G3 firmware TS100R011, TS100R025, TS100P002, TS200R005, TS201R014, and TS201R015 installs an undocumented admin account with a default "!admin" password, which allows remote attackers to gain privileges.
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 Modular Smart Array P2000 G3 firmware versions TS100R011, TS100R025, TS100P002, TS200R005, TS201R014, and TS201R015 contain a hardcoded undocumented administrator account with default password '!admin', enabling remote attackers to gain full administrative privileges on the storage array.
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= ts100p002= ts100r011= ts100r025= ts200r005= ts201r014= ts201r015CVSS 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
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:S/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 device modelAccess the storage array management interface (web GUI or CLI) and verify the model is HP StorageWorks Modular Smart Array P2000 G3. Check the system information or hardware inventory.Affected if Device model is P2000 G3
-
Check the installed firmware versionNavigate to the storage array management interface, typically via web browser to the device IP, and locate the firmware version in System > Overview or similar section. Alternatively, use the CLI command 'show version' or 'show controller' to retrieve firmware information.Affected if Firmware version matches one of: TS100P002, TS100R011, TS100R025, TS200R005, TS201R014, or TS201R015
-
Verify the undocumented administrator account existsAttempt to log into the storage array management interface using the username '!admin' with password '!admin'. This account should not exist in normal deployments but will succeed on affected firmware versions.Affected if Login succeeds with username '!admin' and password '!admin' and grants full administrative access
You are affected if you have a P2000 G3 storage array running any of the listed firmware versions, or if the '!admin' account with password '!admin' successfully authenticates to your device.
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 dataApply HP firmware updates when available; immediately change or disable the default '!admin' account password; restrict network access to the management interfaces via firewall or ACLs until patched.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2010-4115 — 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-2010-4115 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