# CVE-2017-5615: Open redirect in n/a

> Remote attackers can inject HTTP headers via newline characters in redirect locations, potentially enabling phishing or cache poisoning attacks.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r88j-2w5r-2c6x, UBUNTU-CVE-2017-5615

## What is CVE-2017-5615?

CVE-2017-5615 is a medium-severity vulnerability in n/a, published on 3 Mar 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

cgiemail and cgiecho allow remote attackers to inject HTTP headers via a newline character in the redirect location.

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

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

It affects 2 products.


Products: Cpanel Cgiecho, Cpanel Cgiemail.

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

Apply the vendor's patch.

## Is CVE-2017-5615 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-5613](https://insights.sbomify.com/CVE-2017-5613/): Code injection in n/a (high 7.8)
- [CVE-2017-5616](https://insights.sbomify.com/CVE-2017-5616/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5615 is a medium-severity vulnerability in n/a, published on 3 Mar 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-5615 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-5615/ (Markdown: https://insights.sbomify.com/CVE-2017-5615/index.md)
```

## Sources

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

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