{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-38199 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2023-38199 is a critical vulnerability in n/a, published on 13 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-38199 and fix it if it is affected.\n\nWhat it is: CVE-2023-38199 is a critical vulnerability in n/a, published on 13 Jul 2023. 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-2023-38199 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-2023-38199/ (Markdown: https://insights.sbomify.com/CVE-2023-38199/index.md)","id":"CVE-2023-38199","markdown":"https://insights.sbomify.com/CVE-2023-38199/index.md","name":"CVE-2023-38199","record":{"aliases":["DEBIAN-CVE-2023-38199","GHSA-662c-vg67-m327","UBUNTU-CVE-2023-38199","openSUSE-SU-2024:13187-1"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"ModSecurity Core Rule Set","requires_auth":"none","summary":"Attackers can bypass WAF protections by sending multiple Content-Type headers, exploiting confusion between the WAF and backend application.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"coreruleset","vendor":"owasp"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"}],"description":"coreruleset (aka OWASP ModSecurity Core Rule Set) through 3.3.4 does not detect multiple Content-Type request headers on some platforms. This might allow attackers to bypass a WAF with a crafted payload, aka \"Content-Type confusion\" between the WAF and the backend application. This occurs when the web application relies on only the last Content-Type header. Other platforms may reject the additional Content-Type header or merge conflicting headers, leading to detection as a malformed header.","ecosystems":[],"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":"Security feature bypass in n/a","id":"CVE-2023-38199","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Keylime: registrar is subject to a dos against ssl connections","id":"CVE-2023-38200"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2023-38198"},"products":["n/a"],"published":"2023-07-13","related":[],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-30","vendors":["n/a"]},"summary":"Attackers can bypass WAF protections by sending multiple Content-Type headers, exploiting confusion between the WAF and backend application.","url":"https://insights.sbomify.com/CVE-2023-38199/"}