# CVE-2017-6508: Other in n/a

> Remote attackers can inject arbitrary HTTP headers via CRLF sequences in URLs, potentially bypassing security controls or modifying requests.

- **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:** 7 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-6508, CLEANSTART-2026-ZT91139, DEBIAN-CVE-2017-6508, DLA-851-1, GHSA-vmw7-mxgc-c8qm, MGASA-2017-0104, SUSE-SU-2017:0799-1, SUSE-SU-2017:0800-1, UBUNTU-CVE-2017-6508

## What is CVE-2017-6508?

CVE-2017-6508 is a medium-severity vulnerability in n/a, published on 7 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

CRLF injection vulnerability in the url_parse function in url.c in Wget through 1.19.1 allows remote attackers to inject arbitrary HTTP headers via CRLF sequences in the host subcomponent of a URL.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wget` | SUSE:Linux Enterprise Desktop 12 SP1 | All versions | 1.14-20.1 |
| `wget` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 1.14-20.1 |
| `wget` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 1.11.4-1.40.1 |
| `wget-openssl1` | SUSE:Linux Enterprise Server 11-SECURITY | All versions | 1.11.4-1.40.1 |
| `wget` | SUSE:Linux Enterprise Server 12 SP1 | All versions | 1.14-20.1 |
| `wget` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 1.14-20.1 |
| `wget` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 1.14-20.1 |
| `wget` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 1.11.4-1.40.1 |
| `wget` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.14-20.1 |
| `wget` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.14-20.1 |

Products: Gnu Wget.

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

Upgrade to a fixed version.

## Is CVE-2017-6508 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-5953](https://insights.sbomify.com/CVE-2019-5953/): Memory corruption in GNU Wget (critical 9.8)
- [CVE-2014-4877](https://insights.sbomify.com/CVE-2014-4877/): Path traversal in n/a (critical 9.3)
- [CVE-2024-38428](https://insights.sbomify.com/CVE-2024-38428/): Other in n/a (critical 9.1)
- [CVE-2026-58469](https://insights.sbomify.com/CVE-2026-58469/): GNU Wget 1.25.0 Heap Buffer Underread via Metalink URL Parsing (high 8.7)
- [CVE-2016-7098](https://insights.sbomify.com/CVE-2016-7098/): Race condition in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6508 is a medium-severity vulnerability in n/a, published on 7 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-6508 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-6508/ (Markdown: https://insights.sbomify.com/CVE-2017-6508/index.md)
```

## Sources

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

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