Vulnerability in com.hotels.styx:styx-api (CVE-2020-6858)
Summary
Vulnerability in com.hotels.styx:styx-api (CVE-2020-6858). Data can be tampered with by attackers. Exploitable via com.hotels.styx.api.HttpHeaders.Builder. Mitigation: upgrade to 1.0.0-rc1 or later.
Original description
The description as published by the source.
Vulnerability
Styx is vulnerable to CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting').
Vulnerable Component
The vulnerable component is the com.hotels.styx.api.HttpHeaders.Builder due to disabling the HTTP Header validation built into Netty in these locations:
new DefaultHttpHeaders(false) disables the built-in validation in Netty. Either use the default constructor or new DefaultHttpHeaders(true instead.
Additionally, another vulnerable component is the StyxToNettyResponseTranslator due to also disabling the HTTP Header validation built into netty in this location.
DefaultHttpResponse nettyResponse = new DefaultHttpResponse(version, httpResponseStatus, false);
new DefaultHttpResponse(version, httpResponseStatus, false); disables the built-in validation in Netty. Please use the constructor new DefaultHttpResponse(version, httpResponseStatus, true);
Proof of Concept
The following test plugin proves that…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-6858 has been found in com.hotels.styx:styx-api.
Attackers can target a specific entry point like com.hotels.styx.api.HttpHeaders.Builder over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade com.hotels.styx:styx-api to 1.0.0-rc1 or later.
If unsure, ask your IT team or search "com.hotels.styx:styx-api CVE-2020-6858" on the vendor's site.
CVE-2020-6858 (com.hotels.styx:styx-api) — CWE-74
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: com.hotels.styx.api.HttpHeaders.Builder
Patched: 1.0.0-rc1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-74) exists in com.hotels.styx:styx-api. Attackers reach the vulnerable code path via com.hotels.styx.api.HttpHeaders.Builder without authentication.
Check the vendor advisory for the affected versions of com.hotels.styx:styx-api. Attack surface: com.hotels.styx.api.HttpHeaders.Builder.
Severity: ?. Data can be tampered with by attackers.
Update to 1.0.0-rc1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.hotels.styx:styx-api を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.hotels.styx:styx-api to 1.0.0-rc1ステージング環境で 1.0.0-rc1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web twitter.com