{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8725 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8725 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8725 is a high-severity memory corruption vulnerability in Microsoft Office, published on 13 Sep 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-8725 and fix it if it is affected.\n\nWhat it is: CVE-2017-8725 is a high-severity memory corruption vulnerability in Microsoft Office, published on 13 Sep 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-8725 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-2017-8725/ (Markdown: https://insights.sbomify.com/CVE-2017-8725/index.md)","id":"CVE-2017-8725","markdown":"https://insights.sbomify.com/CVE-2017-8725/index.md","name":"CVE-2017-8725","record":{"aliases":["GHSA-wh24-m3cp-5hcg"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Microsoft Office Publisher","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by exploiting a memory handling flaw in Microsoft Publisher.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"publisher","vendor":"microsoft"}],"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":"A remote code execution vulnerability exists in Microsoft Publisher 2007 Service Pack 3 and Microsoft Publisher 2010 Service Pack 2 when they fail to properly handle objects in memory, aka \"Microsoft Office Publisher Remote Code Execution\".","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-8725","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":"Memory corruption in Microsoft Edge","id":"CVE-2017-8726"},"packages":[],"prev":{"headline":"Open redirect in Microsoft Edge","id":"CVE-2017-8724"},"products":["Microsoft Office"],"published":"2017-09-13","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-1318","kev_date_added":null,"published":"2013-05-15"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-1319","kev_date_added":null,"published":"2013-05-15"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-1320","kev_date_added":null,"published":"2013-05-15"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-1322","kev_date_added":null,"published":"2013-05-15"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-0102","kev_date_added":null,"published":"2008-02-12"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2007-1117","kev_date_added":null,"published":"2007-02-27"},{"cvss_score":9.3,"headline":"Null dereference in n/a","id":"CVE-2014-1759","kev_date_added":null,"published":"2014-04-08"}],"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-09-17","vendors":["Microsoft Corporation"]},"summary":"Remote attackers can execute arbitrary code by exploiting a memory handling flaw in Microsoft Publisher.","url":"https://insights.sbomify.com/CVE-2017-8725/"}