# CVE-2017-1375: Weak cryptography in n/a

> Weak cryptographic algorithms in IBM Storwize V7000 Unified allow attackers to decrypt highly sensitive information.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-946g-xg2p-c79m

## What is CVE-2017-1375?

CVE-2017-1375 is a high-severity vulnerability in n/a, published on 24 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM System Storage Storwize V7000 Unified (V7000U) 1.5 and 1.6 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 126868.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2017-1375?

It affects 1 product.


Products: Ibm Storwize Unified V7000 Software.

## How do I fix CVE-2017-1375?

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

## Is CVE-2017-1375 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-4293](https://insights.sbomify.com/CVE-2019-4293/): Information disclosure in Storwize V7000 Unified (2073) (medium 5.3)
- [CVE-2018-1467](https://insights.sbomify.com/CVE-2018-1467/): Information disclosure in Storwize V7000 Unified (2073) (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1375 and fix it if it is affected.

What it is: CVE-2017-1375 is a high-severity vulnerability in n/a, published on 24 Oct 2017. 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-2017-1375 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-2017-1375/ (Markdown: https://insights.sbomify.com/CVE-2017-1375/index.md)
```

## Sources

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

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