dbcve.org
San\/iqApplication · Hp

CVE-2013-2352

HIGH · 9.4 CVSS v2.0 Published 2013-07-10
Fix available
A fix is available. Upgrade to after 10.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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
LeftHand OS (aka SAN iQ) 10.5 and earlier on HP StoreVirtual Storage devices does not provide a mechanism for disabling the HP Support challenge-response root-login feature, which makes it easier for remote attackers to obtain administrative access by leveraging knowledge of an unused one-time password.

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 confidence

LeftHand OS (SAN iQ) versions 10.5 and earlier on HP StoreVirtual Storage devices contains a hardcoded/backdoor root-login mechanism using a challenge-response one-time password system. The system provides no administrative mechanism to disable this HP Support feature, allowing remote attackers with knowledge of an unused OTP to gain full administrative/root access.

MitigationImplement strict network access controls (firewall rules, ACLs) to limit exposure of the management interfaces to only authorized networks, or isolate the storage management network from untrusted networks. Consider whether HP Support access is required and coordinate with HP for updated firmware if available.

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
San\/iqApplication
Affected:<= 10.5= 8.0= 8.1= 8.5= 9.0= 9.5= 10.0

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
None
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:N/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 installed LeftHand OS version
    Access the storage system management interface and navigate to System > Diagnostics > System Information, or use the 'cliqr' CLI command 'show system' to display the OS version. Alternatively, check the boot screen or system startup logs for the firmware version.
    Affected if The displayed version is 8.0, 8.1, 8.5, 9.0, 9.5, 10.0, or any version 10.5 or earlier.
  2. Confirm product is HP StoreVirtual or LeftHand SAN iQ
    Verify the device model through the management interface under System > Diagnostics > System Information, or by checking the physical device label/console output.
    Affected if The device is identified as HP StoreVirtual Storage or LeftHand SAN iQ running the affected versions listed above.
  3. Check network exposure of management interfaces
    Review firewall rules, ACLs, or network segmentation configurations to determine if TCP ports 22 (SSH), 23 (Telnet), or 443/80 (web management) for the storage system are accessible from untrusted networks or the internet.
    Affected if Management interfaces are reachable from networks outside the trusted administrative network, increasing exploitability.
  4. Review authentication logs for anomalous root logins
    Examine system audit logs under System > Diagnostics > Log Viewer, specifically looking for authentication events with unusual timestamps, source IPs outside expected ranges, or successful root-level SSH logins.
    Affected if There are root login events that cannot be traced to known administrators or that occurred via the OTP-based backdoor mechanism.
  5. Verify if HP Support access feature is configured
    Check System > Settings > Support or similar management sections for HP Support remote access configuration. There is no administrative toggle to disable this feature in affected versions.
    Affected if HP Support remote access is enabled and the device is network-accessible, making the backdoor potentially exploitable.

The environment is affected if the installed LeftHand OS/SAN iQ version is 8.0, 8.1, 8.5, 9.0, 9.5, 10.0, or any version 10.5 or earlier on HP StoreVirtual Storage, and the management interface is accessible from untrusted networks.

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

Implement strict network access controls (firewall rules, ACLs) to limit exposure of the management interfaces to only authorized networks, or isolate the storage management network from untrusted networks. Consider whether HP Support access is required and coordinate with HP for updated firmware if available.

Fix this in San\/iq Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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