# CVE-2017-8968: A remote execution of arbitrary code vulnerability has been identified in HPE RESTful Interface Tool 1.5, 2.0 (hprest-1.5-79.x86_64.rpm, ilo


- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q6h5-mv9j-hj66

## What is CVE-2017-8968?

CVE-2017-8968 is a high-severity vulnerability in Hewlett Packard Enterprise HPE RESTful Interface Tool, published on 6 Aug 2018. 

### Official description

A remote execution of arbitrary code vulnerability has been identified in HPE RESTful Interface Tool 1.5, 2.0 (hprest-1.5-79.x86_64.rpm, ilorest-2.0-403.x86_64.rpm). The issue is resolved in iLOREST v2.1 or subsequent versions.

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

It affects 1 product.


Products: Hp Restful Interface Tool.

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

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

## Is CVE-2017-8968 being exploited?

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

## Other vulnerabilities in Hewlett Packard Enterprise HPE RESTful Interface Tool

- [CVE-2016-2023](https://insights.sbomify.com/CVE-2016-2023/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8968 is a high-severity vulnerability in Hewlett Packard Enterprise HPE RESTful Interface Tool, published on 6 Aug 2018. 
Exploitation: There is no known exploitation of CVE-2017-8968 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise HPE RESTful Interface Tool. 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-8968/ (Markdown: https://insights.sbomify.com/CVE-2017-8968/index.md)
```

## Sources

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

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