{"answers":{"affected":"2 open source packages ship an affected version, including react/http. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36032 in the wild and no public exploit code.","fix":"Upgrade react/http to 1.7.0 or later.","what":"CVE-2022-36032 is a medium-severity vulnerability in reactphp http, published on 6 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36032 and fix it if it is affected.\n\nWhat it is: CVE-2022-36032 is a medium-severity vulnerability in reactphp http, published on 6 Sep 2022. 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-2022-36032 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- react/http (Packagist): affected from 0.7.0; fixed in 1.7.0\n- react/http (Packagist): affected from 0.7.0; fixed in 1.7.0\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-2022-36032/ (Markdown: https://insights.sbomify.com/CVE-2022-36032/index.md)","id":"CVE-2022-36032","markdown":"https://insights.sbomify.com/CVE-2022-36032/index.md","name":"CVE-2022-36032","record":{"aliases":["GHSA-w3w9-vrf5-8mx8","UBUNTU-CVE-2022-36032"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"ReactPHP HTTP server","requires_auth":"none","summary":"Attackers can bypass cookie security prefixes by exploiting URL decoding flaws in ReactPHP's HTTP server, allowing them to forge secure cookies.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"http","vendor":"reactphp"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-565","name":"Reliance on Cookies without Validation and Integrity Checking"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"ReactPHP HTTP is a streaming HTTP client and server implementation for ReactPHP. In ReactPHP's HTTP server component versions starting with 0.7.0 and prior to 1.7.0, when ReactPHP is processing incoming HTTP cookie values, the cookie names are url-decoded. This may lead to cookies with prefixes like `__Host-` and `__Secure-` confused with cookies that decode to such prefix, thus leading to an attacker being able to forge cookie which is supposed to be secure. This issue is fixed in ReactPHP HTTP version 1.7.0. As a workaround, Infrastructure or DevOps can place a reverse proxy in front of the ReactPHP HTTP server to filter out any unexpected `Cookie` request headers.","ecosystems":["Packagist"],"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":"ReactPHP's HTTP server parses encoded cookie names so malicious `__Host-` and `__Secure-` cookies can be sent","id":"CVE-2022-36032","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":2,"n_references":4,"next":{"headline":"jsoup may not sanitize Cross-Site Scripting (XSS) attempts if SafeList.preserveRelativeLinks is enabled","id":"CVE-2022-36033"},"packages":[{"ecosystem":"Packagist","fixed":["1.7.0"],"introduced":["0.7.0"],"last_affected":[],"package":"react/http","purl":null,"source":"GHSA-w3w9-vrf5-8mx8"},{"ecosystem":"Packagist","fixed":["1.7.0"],"introduced":["0.7.0"],"last_affected":[],"package":"react/http","purl":"pkg:composer/react/http","source":"GHSA-w3w9-vrf5-8mx8"}],"prev":{"headline":"Unhandled exception on illegal filename_disk value","id":"CVE-2022-36031"},"products":["http"],"published":"2022-09-06","related":[{"cvss_score":5.3,"headline":"ReactPHP's HTTP server continues parsing unused multipart parts after reaching limits","id":"CVE-2023-26044","kev_date_added":null,"published":"2023-05-17"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["reactphp"]},"summary":"Attackers can bypass cookie security prefixes by exploiting URL decoding flaws in ReactPHP's HTTP server, allowing them to forge secure cookies.","url":"https://insights.sbomify.com/CVE-2022-36032/"}