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.
CVE-2013-6737
NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 2%CVSS: —Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- —
- EG Score
- 0.0(none)
- EPSS
- 73.4%
- KEV
- Not listed
Published
June 21, 2014
Last Modified
May 6, 2026
References (6)
- psirt@ushttp://www.ibm.com/support/docview.wss?uid=ssg1S1004676
- psirt@ushttp://www.securityfocus.com/bid/68133
- psirt@ushttps://exchange.xforce.ibmcloud.com/vulnerabilities/89782
- af854a3a-2127-422b-91ae-364da2661108http://www.ibm.com/support/docview.wss?uid=ssg1S1004676
- af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/68133
- af854a3a-2127-422b-91ae-364da2661108https://exchange.xforce.ibmcloud.com/vulnerabilities/89782
Frequently asked(4)
What is CVE-2013-6737?
CVE-2013-6737 is a none vulnerability published on June 21, 2014. 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.
When was CVE-2013-6737 disclosed?
CVE-2013-6737 was first published in the National Vulnerability Database on June 21, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-6737 actively exploited?
CVE-2013-6737 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 73.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2013-6737?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-6737, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2013-6737
Is Your Infrastructure Affected by CVE-2013-6737?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.