# CVE-2017-8989: Open redirect in HPE Icewall DFW

> Remote attackers can exploit an open redirect vulnerability in HPE IceWall SSO to redirect users to malicious sites.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 6 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7w6j-444c-wpvq

## What is CVE-2017-8989?

CVE-2017-8989 is a critical vulnerability in Hewlett Packard Enterprise HPE Icewall DFW, published on 6 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security vulnerability in HPE IceWall SSO Dfw 10.0 and 11.0 on RHEL, HP-UX, and Windows could be exploited remotely to allow URL Redirection.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: Hp Icewall Sso.

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

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

## Is CVE-2017-8989 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8989 is a critical vulnerability in Hewlett Packard Enterprise HPE Icewall DFW, published on 6 Aug 2018. 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-8989 in the wild and no public exploit code.

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

## Sources

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

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