{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2015-1770 in the wild since at least 28 Mar 2022.","fix":"No fix has been published for CVE-2015-1770 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 18 Apr 2022.","what":"CVE-2015-1770 is a high-severity memory corruption vulnerability in Microsoft Office, published on 10 Jun 2015. 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-2015-1770 and fix it if it is affected.\n\nWhat it is: CVE-2015-1770 is a high-severity memory corruption vulnerability in Microsoft Office, published on 10 Jun 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: Yes. Attackers have exploited CVE-2015-1770 in the wild since at least 28 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-2015-1770/ (Markdown: https://insights.sbomify.com/CVE-2015-1770/index.md)","id":"CVE-2015-1770","markdown":"https://insights.sbomify.com/CVE-2015-1770/index.md","name":"CVE-2015-1770","record":{"aliases":["GHSA-63xg-2ggr-xj5w"],"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 via crafted documents due to uninitialized memory use in Microsoft Office.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"office","vendor":"microsoft"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-824","name":"Access of Uninitialized Pointer"}],"description":"Microsoft Office 2013 SP1 and 2013 RT SP1 allows remote attackers to execute arbitrary code via a crafted Office document, aka \"Microsoft Office Uninitialized Memory Use Vulnerability.\"","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":null,"headline":"Microsoft Office Uninitialized Memory Use","id":"CVE-2015-1770","indexable":true,"kev":{"dateAdded":"2022-03-28","dueDate":"2022-04-18","knownRansomwareCampaignUse":"Unknown","product":"Office","requiredAction":"Apply updates per vendor instructions.","vendorProject":"Microsoft","vulnerabilityName":"Microsoft Office Uninitialized Memory Use Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"microsoft:office","products":["microsoft:office"],"type":"memory_corruption","year":"2015"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2015-1771"},"packages":[],"prev":{"headline":"Microsoft Windows Mount Manager Privilege Escalation","id":"CVE-2015-1769"},"products":["n/a"],"published":"2015-06-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 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":"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)"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code via crafted documents due to uninitialized memory use in Microsoft Office.","url":"https://insights.sbomify.com/CVE-2015-1770/"}