# CVE-2013-2352: Auth bypass in n/a

> Remote attackers can gain administrative access to HP StoreVirtual Storage devices by exploiting a disabled challenge-response root-login feature.

- **Severity:** Critical 9.4 (`AV:N/AC:L/Au:N/C:N/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-23pc-m5mw-j4cc

## What is CVE-2013-2352?

CVE-2013-2352 is a critical authentication bypass vulnerability in n/a, published on 10 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-255

## Which versions are affected by CVE-2013-2352?

It affects 1 product.


Products: Hp San\/Iq.

## How do I fix CVE-2013-2352?

No fix has been published for CVE-2013-2352 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-2352 being exploited?

There is no known exploitation of CVE-2013-2352 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2012-2986](https://insights.sbomify.com/CVE-2012-2986/): Command injection in n/a (high 7.7)
- [CVE-2012-4361](https://insights.sbomify.com/CVE-2012-4361/): Command injection in n/a (high 7.7)
- [CVE-2012-4362](https://insights.sbomify.com/CVE-2012-4362/): Hardcoded credentials in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2352 and fix it if it is affected.

What it is: CVE-2013-2352 is a critical authentication bypass vulnerability in n/a, published on 10 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2352 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-2352/ (Markdown: https://insights.sbomify.com/CVE-2013-2352/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-2352
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-2352
- OSV: https://osv.dev/vulnerability/CVE-2013-2352

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-2352/
Summaries are generated and may contain mistakes; the official description above is the record.