{"answers":{"affected":"It affects 8 products.","exploited":"There is no known exploitation of CVE-2019-1201 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-1201 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-1201 is a high-severity memory corruption vulnerability in Microsoft Office, published on 14 Aug 2019. 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-2019-1201 and fix it if it is affected.\n\nWhat it is: CVE-2019-1201 is a high-severity memory corruption vulnerability in Microsoft Office, published on 14 Aug 2019. 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-2019-1201 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-2019-1201/ (Markdown: https://insights.sbomify.com/CVE-2019-1201/index.md)","id":"CVE-2019-1201","markdown":"https://insights.sbomify.com/CVE-2019-1201/index.md","name":"CVE-2019-1201","record":{"aliases":["GHSA-mhjc-pqhq-cf8c"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Microsoft Word","requires_auth":"none","summary":"An attacker can execute arbitrary code by tricking a user into opening a specially crafted Microsoft Word file, potentially compromising the user's system.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"office","vendor":"microsoft"},{"product":"office_365_proplus","vendor":"microsoft"},{"product":"office_online_server","vendor":"microsoft"},{"product":"office_web_apps","vendor":"microsoft"},{"product":"office_web_apps_server","vendor":"microsoft"},{"product":"sharepoint_enterprise_server","vendor":"microsoft"},{"product":"sharepoint_server","vendor":"microsoft"},{"product":"word","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":[],"description":"A remote code execution vulnerability exists in Microsoft Word software when it fails to properly handle objects in memory. An attacker who successfully exploited the vulnerability could use a specially crafted file to perform actions in the security context of the current user. The file could then take actions on behalf of the logged-on user with the same permissions as the current user.\nTo exploit the vulnerability, a user must open a specially crafted file with an affected version of Microsoft Word software.\nTwo possible email attack scenarios exist for this vulnerability:\n•\tWith the first email attack scenario, an attacker could send a specially crafted email message to the user and wait for the user to click on the message. When the message renders via Microsoft Word in the Outlook Preview Pane, an attack could be triggered.\n•\tWith the second scenario, an attacker could attach a specially crafted file to an email, send it to a user, and convince them to open it.\nIn a web-based attack scenario, an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) that contains a specially crafted file that is designed to exploit the vulnerability. However, an attacker would have no way to force the user to visit the website. Instead, an attacker would have to convince the user to click a link, typically by way of an enticement in an email or other message, and then convince the user to open the specially crafted file.\nThe security update addresses the vulnerability by correcting how Microsoft Word handles files in memory.\nFor users who view their emails in Outlook, the Preview Pane attack vector can be mitigated by disabling this feature. The following registry keys can be set to disable the Preview Pane in Outlook on Windows, either via manual editing of the registry or by modifying Group Policy.\nNote Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the \u0026quot;Changing Keys and Values\u0026quot; Help topic in Registry Editor (Regedit.exe) or view the \u0026quot;Add and Delete Information in the Registry\u0026quot; and \u0026quot;Edit Registry Data\u0026quot; Help topics in Regedt32.exe.\nOutlook 2010:\nHKEY_CURRENT_USER\\Software\\Microsoft\\Office\\14.0\\Outlook\\Options\nDWORD: DisableReadingPane\nValue: 1\nOutlook 2013:\nHKEY_CURRENT_USER\\Software\\Microsoft\\Office\\15.0\\Outlook\\Options\nDWORD: DisableReadingPane\nValue: 1\nOutlook 2016, Outlook 2019, and Office 365 ProPlus:\nHKEY_CURRENT_USER\\Software\\Microsoft\\Office\\16.0\\Outlook\\Options\nDWORD: DisableReadingPane\nValue: 1","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":"Microsoft Word Remote Code Execution Vulnerability","id":"CVE-2019-1201","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:office","products":["microsoft:office","microsoft:office_365_proplus","microsoft:office_online_server","microsoft:office_web_apps","microsoft:office_web_apps_server","microsoft:sharepoint_enterprise_server","microsoft:sharepoint_server","microsoft:word"],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"SharePoint Information Disclosure Vulnerability","id":"CVE-2019-1202"},"packages":[],"prev":{"headline":"Microsoft Outlook Remote Code Execution Vulnerability","id":"CVE-2019-1200"},"products":["Microsoft Office 2010 Service Pack 2","Microsoft Office 2016 for Mac","Microsoft Office 2019","Microsoft Office 2019 for Mac","Microsoft Office Online Server","Microsoft Office Web Apps 2010 Service Pack 2","Microsoft Office Web Apps Server 2013 Service Pack 1","Microsoft SharePoint Enterprise Server 2013 Service Pack 1","Microsoft SharePoint Enterprise Server 2016","Microsoft SharePoint Server 2010 Service Pack 2","Microsoft SharePoint Server 2019","Microsoft Word 2010 Service Pack 2","Microsoft Word 2013 Service Pack 1","Microsoft Word 2016","Office 365 ProPlus"],"published":"2019-08-14","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"},{"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":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Microsoft"]},"summary":"An attacker can execute arbitrary code by tricking a user into opening a specially crafted Microsoft Word file, potentially compromising the user's system.","url":"https://insights.sbomify.com/CVE-2019-1201/"}