{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2017-0027 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-0027 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-0027 is a medium-severity vulnerability in Microsoft Excel, published on 17 Mar 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-0027 and fix it if it is affected.\n\nWhat it is: CVE-2017-0027 is a medium-severity vulnerability in Microsoft Excel, published on 17 Mar 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-0027 in the wild and no public exploit code.\n\nAffected product: Microsoft Excel. 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-0027/ (Markdown: https://insights.sbomify.com/CVE-2017-0027/index.md)","id":"CVE-2017-0027","markdown":"https://insights.sbomify.com/CVE-2017-0027/index.md","name":"CVE-2017-0027","record":{"aliases":["GHSA-5f8f-6qqr-hqrc"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Microsoft Office Excel","requires_auth":"none","summary":"Remote attackers can obtain sensitive information from process memory by tricking users into opening a crafted Office document.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"excel","vendor":"microsoft"},{"product":"office_compatibility_pack","vendor":"microsoft"},{"product":"sharepoint_server","vendor":"microsoft"}],"cvss":{"score":4.7,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Microsoft Excel 2007 SP3, Excel 2010 SP2, Excel 2013 RT SP1, Excel 2016, Office Compatibility Pack SP3, and Excel Services on SharePoint Server 2013 SP1 allow remote attackers to obtain sensitive information from process memory via a crafted Office document, aka \"Microsoft Office Information Disclosure Vulnerability.\"","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":"Information disclosure in Office","id":"CVE-2017-0027","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:excel","products":["microsoft:excel","microsoft:office_compatibility_pack","microsoft:sharepoint_server"],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in Microsoft ChakraCore","id":"CVE-2017-0028"},"packages":[],"prev":{"headline":"Privilege escalation in Win32k","id":"CVE-2017-0026"},"products":["Office"],"published":"2017-03-17","related":[{"cvss_score":8.8,"headline":"Microsoft Excel Remote Code Execution","id":"CVE-2019-1297","kev_date_added":"2022-03-03","published":"2019-09-11"},{"cvss_score":8.8,"headline":"Microsoft Office Remote Code Execution","id":"CVE-2009-0238","kev_date_added":"2026-04-14","published":"2009-02-25"},{"cvss_score":7.8,"headline":"Microsoft Office Security Feature Bypass","id":"CVE-2016-7262","kev_date_added":"2022-03-03","published":"2016-12-20"},{"cvss_score":7.8,"headline":"Microsoft Excel Featheader Record Memory Corruption","id":"CVE-2009-3129","kev_date_added":"2022-03-03","published":"2009-11-11"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2008-0081","kev_date_added":null,"published":"2008-01-16"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2015-6040","kev_date_added":null,"published":"2015-12-09"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2015-6122","kev_date_added":null,"published":"2015-12-09"}],"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-08-05","vendors":["Microsoft Corporation"]},"summary":"Remote attackers can obtain sensitive information from process memory by tricking users into opening a crafted Office document.","url":"https://insights.sbomify.com/CVE-2017-0027/"}