# CVE-2020-6858: HTTP Response Splitting in Styx

> Attackers can inject CRLF sequences into HTTP response headers, potentially enabling cache poisoning or XSS, affecting Hotels Styx users.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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:** 12 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6v7p-v754-j89v

## What is CVE-2020-6858?

CVE-2020-6858 is a medium-severity vulnerability in n/a, published on 12 Mar 2020. 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

Hotels Styx through 1.0.0.beta8 allows HTTP response splitting due to CRLF Injection. This is exploitable if untrusted user input can appear in a response header.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2020-6858?

2 open source packages ship an affected version, including com.hotels.styx:styx-api. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.hotels.styx:styx-api` | Maven | All versions | 1.0.0-rc1 |
| `com.hotels.styx:styx-api` | Maven | All versions | 1.0.0-rc1 |

Products: Hotels Styx.

## How do I fix CVE-2020-6858?

Upgrade com.hotels.styx:styx-api to 1.0.0-rc1 or later.

## Is CVE-2020-6858 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6858 and fix it if it is affected.

What it is: CVE-2020-6858 is a medium-severity vulnerability in n/a, published on 12 Mar 2020. 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-2020-6858 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.hotels.styx:styx-api (Maven): affected all versions; fixed in 1.0.0-rc1
- com.hotels.styx:styx-api (Maven): affected all versions; fixed in 1.0.0-rc1

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-2020-6858/ (Markdown: https://insights.sbomify.com/CVE-2020-6858/index.md)
```

## Sources

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

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