{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2017-11882 in the wild since at least 3 Nov 2021, including in ransomware campaigns.","fix":"No fix has been published for CVE-2017-11882 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.","what":"CVE-2017-11882 is a high-severity memory corruption vulnerability in Microsoft Office, published on 15 Nov 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-11882 and fix it if it is affected.\n\nWhat it is: CVE-2017-11882 is a high-severity memory corruption vulnerability in Microsoft Office, published on 15 Nov 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-11882 in the wild since at least 3 Nov 2021, including in ransomware campaigns.\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-11882/ (Markdown: https://insights.sbomify.com/CVE-2017-11882/index.md)","id":"CVE-2017-11882","markdown":"https://insights.sbomify.com/CVE-2017-11882/index.md","name":"CVE-2017-11882","record":{"aliases":["GHSA-vjph-m3mp-rqj5"],"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 memory corruption flaw in Microsoft Office applications.","user_interaction":"required","vuln_class":"memory_corruption"},"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-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Microsoft Office 2007 Service Pack 3, Microsoft Office 2010 Service Pack 2, Microsoft Office 2013 Service Pack 1, and Microsoft Office 2016 allow an attacker to run arbitrary code in the context of the current user by failing to properly handle objects in memory, aka \"Microsoft Office Memory Corruption Vulnerability\". This CVE ID is unique from CVE-2017-11884.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2017-11-15","github_poc":36,"max_poc_stars":535,"metasploit":1,"nuclei":0,"refs":[{"date":"2017-11-21T05:55:53Z","kind":"github_poc","ref":"https://github.com/Ridter/CVE-2017-11882","stars":535,"title":"CVE-2017-11882 from https://github.com/embedi/CVE-2017-11882"},{"date":"2017-11-20T16:35:30Z","kind":"github_poc","ref":"https://github.com/embedi/CVE-2017-11882","stars":495,"title":"Proof-of-Concept exploits for CVE-2017-11882"},{"date":"2017-11-21T15:22:41Z","kind":"github_poc","ref":"https://github.com/rip1s/CVE-2017-11882","stars":330,"title":"CVE-2017-11882 Exploit accepts over 17k bytes long command/code in maximum."},{"date":"2018-01-11T09:43:46Z","kind":"github_poc","ref":"https://github.com/rxwx/CVE-2018-0802","stars":270,"title":"PoC Exploit for CVE-2018-0802 (and optionally CVE-2017-11882)"},{"date":"2018-01-12T11:38:33Z","kind":"github_poc","ref":"https://github.com/Ridter/RTF_11882_0802","stars":166,"title":"PoC for CVE-2018-0802 And CVE-2017-11882"},{"date":"2017-11-21T18:17:28Z","kind":"github_poc","ref":"https://github.com/0x09AL/CVE-2017-11882-metasploit","stars":98,"title":"This is a Metasploit module which exploits CVE-2017-11882 using the POC released here : https://embedi.com/blog/skeleton-closet-ms-office-vulnerability-you-didnt-know-about."},{"date":"2017-11-22T01:11:39Z","kind":"github_poc","ref":"https://github.com/starnightcyber/CVE-2017-11882","stars":44,"title":"CVE-2017-11882 exploitation"},{"date":"2017-11-21T09:15:28Z","kind":"github_poc","ref":"https://github.com/BlackMathIT/2017-11882_Generator","stars":34,"title":"CVE-2017-11882 File Generator PoC"}],"tier":"exploited"},"has_fix":null,"headline":"Microsoft Office Memory Corruption","id":"CVE-2017-11882","indexable":true,"kev":{"dateAdded":"2021-11-03","dueDate":"2022-05-03","knownRansomwareCampaignUse":"Known","product":"Office","requiredAction":"Apply updates per vendor instructions.","vendorProject":"Microsoft","vulnerabilityName":"Microsoft Office Memory Corruption Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"microsoft:office","products":["microsoft:office"],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":14,"next":{"headline":"Denial of service in ASP.NET Core","id":"CVE-2017-11883"},"packages":[],"prev":{"headline":"Information disclosure in Windows Kernel","id":"CVE-2017-11880"},"products":["Microsoft Office"],"published":"2017-11-15","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 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":"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 memory corruption flaw in Microsoft Office applications.","url":"https://insights.sbomify.com/CVE-2017-11882/"}