# CVE-2018-1775: Path traversal in FlashSystem 9100 Family

> Authenticated users can download arbitrary files from the operating system in IBM storage virtualization products.

- **Severity:** Medium 6.5 (`CVSS:3.0/A:N/AC:L/AV:N/C:H/I:N/PR:L/S:U/UI:N/E:U/RC:C/RL:T`)
- **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:** 27 Feb 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7657-r953-54qx

## What is CVE-2018-1775?

CVE-2018-1775 is a medium-severity path traversal vulnerability in IBM FlashSystem 9100 Family, published on 27 Feb 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM SAN Volume Controller, IBM Storwize, IBM Spectrum Virtualize and IBM FlashSystem products versions 7.5 through 8.2 could allow an authenticated user to download arbitrary files from the operating system. IBM X-Force ID: 148757.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-1775?

It affects 2 products.


Products: Ibm Spectrum Virtualize Software, Ibm Spectrum Virtualize Software for Public Cloud.

## How do I fix CVE-2018-1775?

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

## Is CVE-2018-1775 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1775 and fix it if it is affected.

What it is: CVE-2018-1775 is a medium-severity path traversal vulnerability in IBM FlashSystem 9100 Family, published on 27 Feb 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1775 in the wild and no public exploit code.

Affected product: IBM FlashSystem 9100 Family. 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-2018-1775/ (Markdown: https://insights.sbomify.com/CVE-2018-1775/index.md)
```

## Sources

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

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