{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2017-0261 in the wild since at least 3 Mar 2022.","fix":"No fix has been published for CVE-2017-0261 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 24 Mar 2022.","what":"CVE-2017-0261 is a high-severity use after free vulnerability in Microsoft Office, published on 12 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-0261 and fix it if it is affected.\n\nWhat it is: CVE-2017-0261 is a high-severity use after free vulnerability in Microsoft Office, published on 12 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: Yes. Attackers have exploited CVE-2017-0261 in the wild since at least 3 Mar 2022.\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-0261/ (Markdown: https://insights.sbomify.com/CVE-2017-0261/index.md)","id":"CVE-2017-0261","markdown":"https://insights.sbomify.com/CVE-2017-0261/index.md","name":"CVE-2017-0261","record":{"aliases":["GHSA-vxg6-wq4c-3428"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Microsoft Office","requires_auth":"none","summary":"Attackers can execute arbitrary code by exploiting a use-after-free flaw in Microsoft Office memory handling.","user_interaction":"required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"office","vendor":"microsoft"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"Microsoft Office 2010 SP2, Office 2013 SP1, and Office 2016 allow a remote code execution vulnerability when the software fails to properly handle objects in memory, aka \"Office Remote Code Execution Vulnerability\". This CVE ID is unique from CVE-2017-0262 and CVE-2017-0281.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2019-03-31","github_poc":2,"max_poc_stars":10,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-03-31T07:29:48Z","kind":"github_poc","ref":"https://github.com/kcufId/eps-CVE-2017-0261","stars":10,"title":"eps漏洞(CVE-2017-0261)漏洞分析"},{"date":"2020-08-22T03:01:51Z","kind":"github_poc","ref":"https://github.com/erfze/CVE-2017-0261","stars":0,"title":"CVE-2017-8570 Exp及利用样本分析"}],"tier":"exploited"},"has_fix":null,"headline":"Microsoft Office Use-After-Free","id":"CVE-2017-0261","indexable":true,"kev":{"dateAdded":"2022-03-03","dueDate":"2022-03-24","knownRansomwareCampaignUse":"Unknown","product":"Office","requiredAction":"Apply updates per vendor instructions.","vendorProject":"Microsoft","vulnerabilityName":"Microsoft Office Use-After-Free Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"microsoft:office","products":["microsoft:office"],"type":"use_after_free","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Microsoft Office Remote Code Execution","id":"CVE-2017-0262"},"packages":[],"prev":{"headline":"Memory corruption in Microsoft Office","id":"CVE-2017-0260"},"products":["Microsoft Office"],"published":"2017-05-12","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"}],"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":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["Microsoft Corporation"]},"summary":"Attackers can execute arbitrary code by exploiting a use-after-free flaw in Microsoft Office memory handling.","url":"https://insights.sbomify.com/CVE-2017-0261/"}