{"answers":{"affected":"3 open source packages ship an affected version, including lief. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-38306 in the wild and no public exploit code.","fix":"Upgrade lief to 0.12.1 or later.","what":"CVE-2022-38306 is a high-severity memory corruption vulnerability in n/a, published on 13 Sep 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-38306 and fix it if it is affected.\n\nWhat it is: CVE-2022-38306 is a high-severity memory corruption vulnerability in n/a, published on 13 Sep 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-38306 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- lief (PyPI): affected all versions up to 0.12.1; no fix listed\n- lief (PyPI): affected all versions up to 0.12.1; no fix listed\n- lief (PyPI): affected all versions; fixed in 0.12.1\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-38306/ (Markdown: https://insights.sbomify.com/CVE-2022-38306/index.md)","id":"CVE-2022-38306","markdown":"https://insights.sbomify.com/CVE-2022-38306/index.md","name":"CVE-2022-38306","record":{"aliases":["GHSA-52xx-r3g2-p8jm","PYSEC-2022-274","UBUNTU-CVE-2022-38306"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"LIEF binary analysis library","requires_auth":"none","summary":"A heap-buffer overflow in the LIEF library allows attackers to cause denial of service or execute arbitrary code via crafted input.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lief","vendor":"lief-project"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"LIEF commit 5d1d643 was discovered to contain a heap-buffer overflow in the component /core/CorePrPsInfo.tcc.","ecosystems":["PyPI"],"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":"LIEF vulnerable to heap based buffer overflow","id":"CVE-2022-38306","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":3,"n_references":1,"next":{"headline":"LIEF contains segmentation violation","id":"CVE-2022-38307"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.12.1"],"package":"lief","purl":null,"source":"GHSA-52xx-r3g2-p8jm"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.12.1"],"package":"lief","purl":"pkg:pypi/lief","source":"GHSA-52xx-r3g2-p8jm"},{"ecosystem":"PyPI","fixed":["0.12.1"],"introduced":["0"],"last_affected":[],"package":"lief","purl":"pkg:pypi/lief","source":"PYSEC-2022-274"}],"prev":{"headline":"File upload in n/a","id":"CVE-2022-38305"},"products":["n/a"],"published":"2022-09-13","related":[{"cvss_score":8.8,"headline":"LIEF heap-buffer-overflow","id":"CVE-2021-32297","kev_date_added":null,"published":"2021-09-20"},{"cvss_score":7.8,"headline":"LIEF vulnerable to heap based buffer overflow via print_binary function","id":"CVE-2022-38495","kev_date_added":null,"published":"2022-09-13"},{"cvss_score":6.5,"headline":"LIEF heap buffer overflow in the LIEF::MachO::BinaryParser::parse_dyldinfo_generic_bind","id":"CVE-2022-43171","kev_date_added":null,"published":"2022-11-17"},{"cvss_score":6.5,"headline":"LIEF vulnerable to denial of service through segmentation fault","id":"CVE-2022-40922","kev_date_added":null,"published":"2022-10-03"},{"cvss_score":6.5,"headline":"LIEF vulnerable to denial of service through segmentation fault","id":"CVE-2022-40923","kev_date_added":null,"published":"2022-09-30"},{"cvss_score":5.5,"headline":"LIEF contains segmentation violation","id":"CVE-2022-38307","kev_date_added":null,"published":"2022-09-13"}],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"A heap-buffer overflow in the LIEF library allows attackers to cause denial of service or execute arbitrary code via crafted input.","url":"https://insights.sbomify.com/CVE-2022-38306/"}