{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2017-8510 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8510 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8510 is a high-severity memory corruption vulnerability in Microsoft Excel, published on 15 Jun 2017. 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-2017-8510 and fix it if it is affected.\n\nWhat it is: CVE-2017-8510 is a high-severity memory corruption vulnerability in Microsoft Excel, published on 15 Jun 2017. 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-2017-8510 in the wild and no public exploit code.\n\nAffected product: Microsoft Excel. 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-8510/ (Markdown: https://insights.sbomify.com/CVE-2017-8510/index.md)","id":"CVE-2017-8510","markdown":"https://insights.sbomify.com/CVE-2017-8510/index.md","name":"CVE-2017-8510","record":{"aliases":["GHSA-r2c6-r964-xg2q"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft Office","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by exploiting improper memory handling in Microsoft Office applications.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"excel","vendor":"microsoft"},{"product":"office","vendor":"microsoft"},{"product":"word","vendor":"microsoft"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka \"Office Remote Code Execution Vulnerability\". This CVE ID is unique from CVE-2017-8509, CVE-2017-8511, CVE-2017-8512, CVE-2017-0260, and CVE-2017-8506.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in Microsoft Office","id":"CVE-2017-8510","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:excel","products":["microsoft:excel","microsoft:office","microsoft:word"],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in Microsoft Office","id":"CVE-2017-8511"},"packages":[],"prev":{"headline":"Memory corruption in Microsoft Office","id":"CVE-2017-8509"},"products":["Microsoft Office"],"published":"2017-06-15","related":[{"cvss_score":8.8,"headline":"Microsoft Excel Remote Code Execution","id":"CVE-2019-1297","kev_date_added":"2022-03-03","published":"2019-09-11"},{"cvss_score":8.8,"headline":"Microsoft Office Remote Code Execution","id":"CVE-2009-0238","kev_date_added":"2026-04-14","published":"2009-02-25"},{"cvss_score":7.8,"headline":"Microsoft Office Security Feature Bypass","id":"CVE-2016-7262","kev_date_added":"2022-03-03","published":"2016-12-20"},{"cvss_score":7.8,"headline":"Microsoft Excel Featheader Record Memory Corruption","id":"CVE-2009-3129","kev_date_added":"2022-03-03","published":"2009-11-11"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2008-0081","kev_date_added":null,"published":"2008-01-16"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2015-6040","kev_date_added":null,"published":"2015-12-09"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2015-6122","kev_date_added":null,"published":"2015-12-09"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Microsoft Corporation"]},"summary":"Remote attackers can execute arbitrary code by exploiting improper memory handling in Microsoft Office applications.","url":"https://insights.sbomify.com/CVE-2017-8510/"}