{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16869 in the wild and no public exploit code.","fix":"No fix published yet.","what":"CVE-2017-16869 is a high-severity denial of service vulnerability in n/a, published on 17 Nov 2017. 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-2017-16869 and fix it if it is affected.\n\nWhat it is: CVE-2017-16869 is a high-severity denial of service vulnerability in n/a, published on 17 Nov 2017. 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-2017-16869 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-2017-16869/ (Markdown: https://insights.sbomify.com/CVE-2017-16869/index.md)","id":"CVE-2017-16869","markdown":"https://insights.sbomify.com/CVE-2017-16869/index.md","name":"CVE-2017-16869","record":{"aliases":["DEBIAN-CVE-2017-16869","GHSA-3j3j-cj56-29p8"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","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 can cause a denial of service in UPX, though the vendor disputes any security implication.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"upx","vendor":"upx"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"p_mach.cpp in UPX 3.94 allows remote attackers to cause a denial of service (invalid memory access and application crash) or possibly have unspecified other impact via a crafted Mach-O file, related to canPack and unpack functions. NOTE: the vendor has stated \"there is no security implication whatsoever.","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":"Denial of service in n/a","id":"CVE-2017-16869","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2017-16870"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2017-16868"},"products":["n/a"],"published":"2017-11-17","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"}],"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-05","vendors":["n/a"]},"summary":"A crafted Mach-O file can cause a denial of service in UPX, though the vendor disputes any security implication.","url":"https://insights.sbomify.com/CVE-2017-16869/"}