# CVE-2014-4811: Auth bypass in n/a

> Remote attackers can reset the administrator password to default via direct request, gaining full administrative access to IBM storage devices.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fqr9-prcq-3jc2

## What is CVE-2014-4811?

CVE-2014-4811 is a high-severity authentication bypass vulnerability in n/a, published on 12 Sep 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Storwize 3500, 3700, 5000, and 7000 devices and SAN Volume Controller 6.x and 7.x before 7.2.0.8 allow remote attackers to reset the administrator superuser password to its default value via a direct request to the administrative IP address.

Weakness: CWE-255

## Which versions are affected by CVE-2014-4811?

It affects 5 products.


Products: Ibm San Volume Controller Software, Ibm Storwize V3500, Ibm Storwize V3700, Ibm Storwize V5000, Ibm Storwize V7000.

## How do I fix CVE-2014-4811?

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

## Is CVE-2014-4811 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-6354](https://insights.sbomify.com/CVE-2012-6354/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-4811 and fix it if it is affected.

What it is: CVE-2014-4811 is a high-severity authentication bypass vulnerability in n/a, published on 12 Sep 2014. 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-2014-4811 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-2014-4811/ (Markdown: https://insights.sbomify.com/CVE-2014-4811/index.md)
```

## Sources

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

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