# CVE-2017-9295: XML external entity in n/a

> Authenticated remote attackers can exploit an XXE vulnerability in Hitachi Device Manager to read arbitrary files on the server.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 29 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3v98-72qw-v7r9

## What is CVE-2017-9295?

CVE-2017-9295 is a medium-severity vulnerability in n/a, published on 29 May 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

XXE vulnerability in Hitachi Device Manager before 8.5.2-01 and Hitachi Replication Manager before 8.5.2-00 allows authenticated remote users to read arbitrary files.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

It affects 1 product.


Products: Hitachi Device Manager.

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

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

## Is CVE-2017-9295 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9294](https://insights.sbomify.com/CVE-2017-9294/): Missing authorization in n/a (critical 9.8)
- [CVE-2023-34142](https://insights.sbomify.com/CVE-2023-34142/): Cleartext Transmission Vulnerability in Hitachi Device Manager (critical 9.0)
- [CVE-2019-17360](https://insights.sbomify.com/CVE-2019-17360/): Denial of service in n/a (high 7.5)
- [CVE-2017-9296](https://insights.sbomify.com/CVE-2017-9296/): Open redirect in n/a (medium 6.1)
- [CVE-2017-9297](https://insights.sbomify.com/CVE-2017-9297/): Open redirect in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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