# CVE-2013-6737: Information disclosure in n/a

> Remote authenticated users can read sensitive customer data from dump files generated during specific hardware faults in IBM Storwize V7000 Unified systems.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m3r4-qvc7-qp3g

## What is CVE-2013-6737?

CVE-2013-6737 is a medium-severity vulnerability in n/a, published on 21 Jun 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM System Storage Storwize V7000 Unified 1.3.x and 1.4.x before 1.4.3.0 does not properly restrict the content of a dump file upon encountering a 1691 hardware fault, which allows remote authenticated users to obtain sensitive customer-data fragments by reading this file after it is copied.

Weakness: CWE-264

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

It affects 2 products.


Products: Ibm Storwize Unified V7000, Ibm Storwize Unified V7000 Software.

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

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

## Is CVE-2013-6737 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-3043](https://insights.sbomify.com/CVE-2014-3043/): Privilege escalation in n/a (medium 6.5)
- [CVE-2014-0875](https://insights.sbomify.com/CVE-2014-0875/): Auth bypass in n/a (low 3.5)
- [CVE-2014-3077](https://insights.sbomify.com/CVE-2014-3077/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6737 is a medium-severity vulnerability in n/a, published on 21 Jun 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6737 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-6737/ (Markdown: https://insights.sbomify.com/CVE-2013-6737/index.md)
```

## Sources

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

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