{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-42472 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-42472 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-42472 is a medium-severity vulnerability in Fortinet Fortios, published on 16 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-42472 and fix it if it is affected.\n\nWhat it is: CVE-2022-42472 is a medium-severity vulnerability in Fortinet Fortios, published on 16 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-42472 in the wild and no public exploit code.\n\nAffected product: Fortinet Fortios. 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-2022-42472/ (Markdown: https://insights.sbomify.com/CVE-2022-42472/index.md)","id":"CVE-2022-42472","markdown":"https://insights.sbomify.com/CVE-2022-42472/index.md","name":"CVE-2022-42472","record":{"aliases":["GHSA-2c29-h3hm-8953"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiOS/FortiProxy","requires_auth":"low_privilege","summary":"Authenticated attackers can perform HTTP response splitting to control response headers and body in Fortinet FortiOS and FortiProxy.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortios","vendor":"fortinet"},{"product":"fortiproxy","vendor":"fortinet"}],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N/E:P/RL:U/RC:C","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"},{"id":"CWE-113","name":"Improper Neutralization of CRLF Sequences in HTTP Headers"}],"description":"A improper neutralization of crlf sequences in http headers ('http response splitting') vulnerability in Fortinet FortiOS 7.2.0 through 7.2.2, FortiOS 7.0.0 through 7.0.8, FortiOS 6.4.0 through 6.4.12, FortiOS 6.2 all versions, FortiOS 6.0 all versions, FortiProxy 7.2.0 through 7.2.1, FortiProxy 7.0.0 through 7.0.7, FortiProxy 2.0.0 through 2.0.10, FortiProxy 1.2 all versions, FortiProxy 01.02 all versions, FortiProxy 1.1 all versions, FortiProxy 01.01 all versions may allow an authenticated and remote attacker to perform an HTTP request splitting attack which gives attackers control of the remaining headers and body of the response.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Other in FortiOS","id":"CVE-2022-42472","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortios","products":["fortinet:fortios","fortinet:fortiproxy"],"type":"other","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Fortinet FortiSOAR","id":"CVE-2022-42473"},"packages":[],"prev":{"headline":"Other in FortiWeb","id":"CVE-2022-42471"},"products":["FortiOS","FortiProxy"],"published":"2023-02-16","related":[{"cvss_score":9.8,"headline":"Fortinet Multiple Products Format String","id":"CVE-2024-23113","kev_date_added":"2024-10-09","published":"2024-02-15"},{"cvss_score":9.8,"headline":"Fortinet Multiple Products Authentication Bypass","id":"CVE-2022-40684","kev_date_added":"2022-10-11","published":"2022-10-18"},{"cvss_score":9.6,"headline":"Fortinet FortiOS and FortiProxy Authentication Bypass","id":"CVE-2024-55591","kev_date_added":"2025-01-14","published":"2025-01-14"},{"cvss_score":9.6,"headline":"Fortinet FortiOS Out-of-Bound Write","id":"CVE-2024-21762","kev_date_added":"2024-02-09","published":"2024-02-09"},{"cvss_score":9.3,"headline":"Fortinet FortiOS Heap-Based Buffer Overflow","id":"CVE-2022-42475","kev_date_added":"2022-12-13","published":"2023-01-02"},{"cvss_score":9.2,"headline":"Fortinet FortiOS and FortiProxy SSL-VPN Heap-Based Buffer Overflow","id":"CVE-2023-27997","kev_date_added":"2023-06-13","published":"2023-06-13"},{"cvss_score":9.1,"headline":"Fortinet Multiple Products Improper Verification of Cryptographic Signature","id":"CVE-2025-59718","kev_date_added":"2025-12-16","published":"2025-12-09"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-22","vendors":["Fortinet"]},"summary":"Authenticated attackers can perform HTTP response splitting to control response headers and body in Fortinet FortiOS and FortiProxy.","url":"https://insights.sbomify.com/CVE-2022-42472/"}