{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2018-8501 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-8501 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-8501 is a high-severity code injection vulnerability in Microsoft Office, published on 10 Oct 2018. 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-2018-8501 and fix it if it is affected.\n\nWhat it is: CVE-2018-8501 is a high-severity code injection vulnerability in Microsoft Office, published on 10 Oct 2018. 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-2018-8501 in the wild and no public exploit code.\n\nAffected product: Microsoft Office. 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-2018-8501/ (Markdown: https://insights.sbomify.com/CVE-2018-8501/index.md)","id":"CVE-2018-8501","markdown":"https://insights.sbomify.com/CVE-2018-8501/index.md","name":"CVE-2018-8501","record":{"aliases":["GHSA-c7pp-xrwf-5qjj"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft PowerPoint","requires_auth":"none","summary":"Attackers can execute arbitrary code by exploiting improper object handling in Microsoft PowerPoint's Protected View mode.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"office","vendor":"microsoft"},{"product":"office_365_proplus","vendor":"microsoft"},{"product":"powerpoint","vendor":"microsoft"},{"product":"powerpoint_viewer","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 PowerPoint software when the software fails to properly handle objects in Protected View, aka \"Microsoft PowerPoint Remote Code Execution Vulnerability.\" This affects Office 365 ProPlus, PowerPoint Viewer, Microsoft Office, Microsoft PowerPoint.","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":"Code injection in Microsoft Office","id":"CVE-2018-8501","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:office","products":["microsoft:office","microsoft:office_365_proplus","microsoft:powerpoint"],"type":"code_injection","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in Microsoft Excel","id":"CVE-2018-8502"},"packages":[],"prev":{"headline":"ChakraCore RCE Vulnerability","id":"CVE-2018-8500"},"products":["Microsoft Office","Microsoft PowerPoint","Office","PowerPoint Viewer"],"published":"2018-10-10","related":[{"cvss_score":8.8,"headline":"Microsoft Office Memory Corruption","id":"CVE-2018-0798","kev_date_added":"2021-11-03","published":"2018-01-10"},{"cvss_score":8.8,"headline":"Microsoft Office Uninitialized Memory Use","id":"CVE-2015-1770","kev_date_added":"2022-03-28","published":"2015-06-10"},{"cvss_score":8.8,"headline":"Microsoft Word Malformed Object Pointer","id":"CVE-2006-2492","kev_date_added":"2022-06-08","published":"2006-05-20"},{"cvss_score":7.8,"headline":"Microsoft Office Memory Corruption","id":"CVE-2018-0802","kev_date_added":"2021-11-03","published":"2018-01-10"},{"cvss_score":7.8,"headline":"Microsoft Office Memory Corruption","id":"CVE-2017-11882","kev_date_added":"2021-11-03","published":"2017-11-15"},{"cvss_score":7.8,"headline":"Microsoft Office Remote Code Execution","id":"CVE-2017-8570","kev_date_added":"2022-02-25","published":"2017-07-11"},{"cvss_score":7.8,"headline":"Microsoft Office Use-After-Free","id":"CVE-2017-0261","kev_date_added":"2022-03-03","published":"2017-05-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Microsoft"]},"summary":"Attackers can execute arbitrary code by exploiting improper object handling in Microsoft PowerPoint's Protected View mode.","url":"https://insights.sbomify.com/CVE-2018-8501/"}