{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-1133 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-1133 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-1133 is a low-severity vulnerability in n/a, published on 16 Jan 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-1133 and fix it if it is affected.\n\nWhat it is: CVE-2016-1133 is a low-severity vulnerability in n/a, published on 16 Jan 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-1133 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2016-1133/ (Markdown: https://insights.sbomify.com/CVE-2016-1133/index.md)","id":"CVE-2016-1133","markdown":"https://insights.sbomify.com/CVE-2016-1133/index.md","name":"CVE-2016-1133","record":{"aliases":["GHSA-mpq7-xv6q-mqgh"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"H2O web server","requires_auth":"none","summary":"Remote attackers can inject HTTP headers and split responses via crafted URIs in the H2O web server, potentially manipulating client interactions.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"h2o","vendor":"dena"}],"cvss":{"score":3.7,"severity":"low","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[],"description":"CRLF injection vulnerability in the on_req function in lib/handler/redirect.c in H2O before 1.6.2 and 1.7.x before 1.7.0-beta3 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via a crafted URI.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Other in n/a","id":"CVE-2016-1133","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2016"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2016-1134"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2016-1132"},"products":["n/a"],"published":"2016-01-16","related":[{"cvss_score":9.8,"headline":"Memory corruption in H2O","id":"CVE-2018-0608","kev_date_added":null,"published":"2018-06-26"},{"cvss_score":9.1,"headline":"Use after free in H2O","id":"CVE-2016-7835","kev_date_added":null,"published":"2017-06-09"},{"cvss_score":8.2,"headline":"H2O vulnerable to read from uninitialized pointer in the reverse proxy handler","id":"CVE-2023-30847","kev_date_added":null,"published":"2023-04-27"},{"cvss_score":7.5,"headline":"Denial of service in H2O","id":"CVE-2017-10868","kev_date_added":null,"published":"2017-12-22"},{"cvss_score":7.5,"headline":"Memory corruption in H2O","id":"CVE-2017-10869","kev_date_added":null,"published":"2017-12-22"},{"cvss_score":7.5,"headline":"Denial of service in H2O","id":"CVE-2017-10908","kev_date_added":null,"published":"2017-12-22"},{"cvss_score":7.5,"headline":"Denial of service in H2O","id":"CVE-2016-4864","kev_date_added":null,"published":"2017-05-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can inject HTTP headers and split responses via crafted URIs in the H2O web server, potentially manipulating client interactions.","url":"https://insights.sbomify.com/CVE-2016-1133/"}