{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-27797 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-27797 is a medium-severity vulnerability in upx, published on 25 Aug 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-2020-27797 and fix it if it is affected.\n\nWhat it is: CVE-2020-27797 is a medium-severity vulnerability in upx, published on 25 Aug 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-2020-27797 in the wild and no public exploit code.\n\nAffected product: upx. 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-2020-27797/ (Markdown: https://insights.sbomify.com/CVE-2020-27797/index.md)","id":"CVE-2020-27797","markdown":"https://insights.sbomify.com/CVE-2020-27797/index.md","name":"CVE-2020-27797","record":{"aliases":["DEBIAN-CVE-2020-27797","GHSA-x97v-6wf2-6ffp","UBUNTU-CVE-2020-27797"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"UPX executable packer","requires_auth":"none","summary":"A crafted Mach-O file causes a null pointer dereference in UPX, leading to a denial of service during processing.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"upx","vendor":"upx"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-763","name":"Release of Invalid Pointer or Reference"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An invalid memory address reference was discovered in the elf_lookup function in p_lx_elf.cpp in UPX 4.0.0 via a crafted Mach-O file.","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":"Null dereference in upx","id":"CVE-2020-27797","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in upx","id":"CVE-2020-27798"},"packages":[],"prev":{"headline":"Memory corruption in upx","id":"CVE-2020-27796"},"products":["upx"],"published":"2022-08-25","related":[{"cvss_score":7.8,"headline":"Memory corruption in upx","id":"CVE-2020-27796","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":7.8,"headline":"Memory corruption in upx","id":"CVE-2020-27799","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":7.8,"headline":"Memory corruption in upx","id":"CVE-2020-27800","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":7.8,"headline":"Memory corruption in upx","id":"CVE-2020-27801","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2019-14296","kev_date_added":null,"published":"2019-07-27"},{"cvss_score":7.8,"headline":"Use after free in n/a","id":"CVE-2018-11243","kev_date_added":null,"published":"2018-05-18"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2017-16869","kev_date_added":null,"published":"2017-11-17"}],"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-04","vendors":["n/a"]},"summary":"A crafted Mach-O file causes a null pointer dereference in UPX, leading to a denial of service during processing.","url":"https://insights.sbomify.com/CVE-2020-27797/"}