{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-8852 exists.","fix":"No fix has been published for CVE-2017-8852 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8852 is a high-severity memory corruption vulnerability in n/a, published on 10 May 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-8852 and fix it if it is affected.\n\nWhat it is: CVE-2017-8852 is a high-severity memory corruption vulnerability in n/a, published on 10 May 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-8852 exists.\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-8852/ (Markdown: https://insights.sbomify.com/CVE-2017-8852/index.md)","id":"CVE-2017-8852","markdown":"https://insights.sbomify.com/CVE-2017-8852/index.md","name":"CVE-2017-8852","record":{"aliases":["GHSA-vcmv-vj68-g3f5"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SAP CAR archive tool","requires_auth":"none","summary":"Heap-based buffer overflow in SAPCAR allows remote code execution via a crafted CAR archive file, requiring users to apply vendor patches.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sapcar","vendor":"sap"}],"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":"SAP SAPCAR 721.510 has a Heap Based Buffer Overflow Vulnerability. It could be exploited with a crafted CAR archive file received from an untrusted remote source. The problem is that the length of data written is an arbitrary number found within the file. The vendor response is SAP Security Note 2441560.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2017-05-10","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2017-05-10","kind":"exploitdb","ref":"41991","stars":null,"title":"SAP SAPCAR 721.510 - Heap Buffer Overflow"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2017-8852","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in n/a","id":"CVE-2017-8853"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2017-8851"},"products":["n/a"],"published":"2017-05-10","related":[{"cvss_score":9.8,"headline":"Other in SAPCAR","id":"CVE-2022-26100","kev_date_added":null,"published":"2022-03-08"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2016-5845","kev_date_added":null,"published":"2016-08-12"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Heap-based buffer overflow in SAPCAR allows remote code execution via a crafted CAR archive file, requiring users to apply vendor patches.","url":"https://insights.sbomify.com/CVE-2017-8852/"}