{"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-40923 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-40923 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-40923 is a medium-severity denial of service vulnerability in n/a, published on 30 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-40923 and fix it if it is affected.\n\nWhat it is: CVE-2022-40923 is a medium-severity denial of service vulnerability in n/a, published on 30 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-40923 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 up to 0.12.1; no fix listed\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-40923/ (Markdown: https://insights.sbomify.com/CVE-2022-40923/index.md)","id":"CVE-2022-40923","markdown":"https://insights.sbomify.com/CVE-2022-40923/index.md","name":"CVE-2022-40923","record":{"aliases":["GHSA-rm2x-hgr8-w343","PYSEC-2022-43139"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"LIEF binary analysis library","requires_auth":"none","summary":"Attackers can cause a denial of service via segmentation fault by providing a crafted MachO file to the LIEF library.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lief","vendor":"lief-project"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A vulnerability in the LIEF::MachO::SegmentCommand::virtual_address function of LIEF v0.12.1 allows attackers to cause a denial of service (DOS) through a segmentation fault via a crafted MachO file.","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":false,"headline":"LIEF vulnerable to denial of service through segmentation fault","id":"CVE-2022-40923","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":3,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2022-40924"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.12.1"],"package":"lief","purl":null,"source":"GHSA-rm2x-hgr8-w343"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.12.1"],"package":"lief","purl":"pkg:pypi/lief","source":"GHSA-rm2x-hgr8-w343"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.12.1"],"package":"lief","purl":"pkg:pypi/lief","source":"PYSEC-2022-43139"}],"prev":{"headline":"LIEF vulnerable to denial of service through segmentation fault","id":"CVE-2022-40922"},"products":["n/a"],"published":"2022-09-30","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","id":"CVE-2022-38306","kev_date_added":null,"published":"2022-09-13"},{"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":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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-20","vendors":["n/a"]},"summary":"Attackers can cause a denial of service via segmentation fault by providing a crafted MachO file to the LIEF library.","url":"https://insights.sbomify.com/CVE-2022-40923/"}