{"answers":{"affected":"2 open source packages ship an affected version, including com.hotels.styx:styx-api. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-6858 in the wild and no public exploit code.","fix":"Upgrade com.hotels.styx:styx-api to 1.0.0-rc1 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2020-6858 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2020-6858 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.hotels.styx:styx-api (Maven): affected all versions; fixed in 1.0.0-rc1\n- com.hotels.styx:styx-api (Maven): affected all versions; fixed in 1.0.0-rc1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-6858/ (Markdown: https://insights.sbomify.com/CVE-2020-6858/index.md)","id":"CVE-2020-6858","markdown":"https://insights.sbomify.com/CVE-2020-6858/index.md","name":"CVE-2020-6858","record":{"aliases":["GHSA-6v7p-v754-j89v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Hotels Styx","requires_auth":"none","summary":"Attackers can inject CRLF sequences into HTTP response headers, potentially enabling cache poisoning or XSS, affecting Hotels Styx users.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"styx","vendor":"hotels"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"HTTP Response Splitting in Styx","id":"CVE-2020-6858","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"other","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2020-6859"},"packages":[{"ecosystem":"Maven","fixed":["1.0.0-rc1"],"introduced":["0"],"last_affected":[],"package":"com.hotels.styx:styx-api","purl":null,"source":"GHSA-6v7p-v754-j89v"},{"ecosystem":"Maven","fixed":["1.0.0-rc1"],"introduced":["0"],"last_affected":[],"package":"com.hotels.styx:styx-api","purl":"pkg:maven/com.hotels.styx/styx-api","source":"GHSA-6v7p-v754-j89v"}],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-6857"},"products":["n/a"],"published":"2020-03-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can inject CRLF sequences into HTTP response headers, potentially enabling cache poisoning or XSS, affecting Hotels Styx users.","url":"https://insights.sbomify.com/CVE-2020-6858/"}