{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-38667 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-38667 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-38667 is a critical use after free vulnerability in n/a, published on 22 Aug 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-38667 and fix it if it is affected.\n\nWhat it is: CVE-2022-38667 is a critical use after free vulnerability in n/a, published on 22 Aug 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-38667 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-2022-38667/ (Markdown: https://insights.sbomify.com/CVE-2022-38667/index.md)","id":"CVE-2022-38667","markdown":"https://insights.sbomify.com/CVE-2022-38667/index.md","name":"CVE-2022-38667","record":{"aliases":["GHSA-g8qv-x989-399f"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Crow HTTP library","requires_auth":"none","summary":"Attackers can achieve code execution via HTTP pipelining due to a use-after-free vulnerability in the Crow HTTP library's connection handling.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"crow","vendor":"crowcpp"}],"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-416","name":"Use After Free"}],"description":"HTTP applications (servers) based on Crow through 1.0+4 may allow a Use-After-Free and code execution when HTTP pipelining is used. The HTTP parser supports HTTP pipelining, but the asynchronous Connection layer is unaware of HTTP pipelining. Specifically, the Connection layer is unaware that it has begun processing a later request before it has finished processing an earlier request.","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":"Use after free in n/a","id":"CVE-2022-38667","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Information disclosure in n/a","id":"CVE-2022-38668"},"packages":[],"prev":{"headline":"SSL/TLS certificate validation unconditionally disabled by Jenkins NS-ND Integration Performance Publisher Plugin","id":"CVE-2022-38666"},"products":["n/a"],"published":"2022-08-22","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2022-34970","kev_date_added":null,"published":"2022-08-04"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2022-38668","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":6.5,"headline":"Other in Crow","id":"CVE-2023-26142","kev_date_added":null,"published":"2023-09-12"},{"cvss_score":6.5,"headline":"Path Traversal","id":"CVE-2021-23514","kev_date_added":null,"published":"2022-01-13"},{"cvss_score":6.5,"headline":"Content Injection","id":"CVE-2021-23824","kev_date_added":null,"published":"2022-01-13"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can achieve code execution via HTTP pipelining due to a use-after-free vulnerability in the Crow HTTP library's connection handling.","url":"https://insights.sbomify.com/CVE-2022-38667/"}