{"answers":{"affected":"3 open source packages ship an affected version, including lief. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31636 exists.","fix":"Upgrade lief to 0.15.0 or later.","what":"CVE-2024-31636 is a low-severity vulnerability in n/a, published on 3 May 2024. 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-2024-31636 and fix it if it is affected.\n\nWhat it is: CVE-2024-31636 is a low-severity vulnerability in n/a, published on 3 May 2024. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31636 exists.\n\nAffected packages and fixed versions:\n- lief (PyPI): affected all versions up to 0.14.1; no fix listed\n- lief (PyPI): affected all versions; fixed in 0.15.0\n- lief (PyPI): affected all versions; fixed in 0.15.0\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-2024-31636/ (Markdown: https://insights.sbomify.com/CVE-2024-31636/index.md)","id":"CVE-2024-31636","markdown":"https://insights.sbomify.com/CVE-2024-31636/index.md","name":"CVE-2024-31636","record":{"aliases":["DEBIAN-CVE-2024-31636","GHSA-377p-g8gr-5wpg","PYSEC-2024-280","UBUNTU-CVE-2024-31636"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"LIEF binary analysis library","requires_auth":"low_privilege","summary":"A local attacker can obtain sensitive information via the name parameter in the machd_reader component of the LIEF library.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lief","vendor":"lief-project"}],"cvss":{"score":3.9,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-457","name":"Use of Uninitialized Variable"}],"description":"An issue in LIEF v.0.14.1 allows a local attacker to obtain sensitive information via the name parameter of the machd_reader.c component.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"LIEF obtain sensitive information via the name parameter","id":"CVE-2024-31636","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-31648"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.14.1"],"package":"lief","purl":"pkg:pypi/lief","source":"PYSEC-2024-280"},{"ecosystem":"PyPI","fixed":["0.15.0"],"introduced":["0"],"last_affected":[],"package":"lief","purl":null,"source":"GHSA-377p-g8gr-5wpg"},{"ecosystem":"PyPI","fixed":["0.15.0"],"introduced":["0"],"last_affected":[],"package":"lief","purl":"pkg:pypi/lief","source":"GHSA-377p-g8gr-5wpg"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-31634"},"products":["n/a"],"published":"2024-05-03","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":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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["n/a"]},"summary":"A local attacker can obtain sensitive information via the name parameter in the machd_reader component of the LIEF library.","url":"https://insights.sbomify.com/CVE-2024-31636/"}