# CVE-2019-1149: Microsoft Graphics Remote Code Execution Vulnerability > Remote code execution via crafted fonts allows attackers to take control of Windows systems, requiring user interaction to view malicious content. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 14 Aug 2019 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-vw2q-fc9j-fxwx ## What is CVE-2019-1149? CVE-2019-1149 is a high-severity memory corruption vulnerability in Microsoft Office, published on 14 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description A remote code execution vulnerability exists when the Windows font library improperly handles specially crafted embedded fonts. An attacker who successfully exploited the vulnerability could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. There are multiple ways an attacker could exploit the vulnerability: In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability and then convince users to view the website. An attacker would have no way to force users to view the attacker-controlled content. Instead, an attacker would have to convince users to take action, typically by getting them to click a link in an email or instant message that takes users to the attacker's website, or by opening an attachment sent through email. In a file-sharing attack scenario, an attacker could provide a specially crafted document file designed to exploit the vulnerability and then convince users to open the document file. The security update addresses the vulnerability by correcting how the Windows font library handles embedded fonts. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2019-1149? It affects 9 products. Products: Microsoft Office, Microsoft Windows 10, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019. ## How do I fix CVE-2019-1149? No fix has been published for CVE-2019-1149 yet. Limit exposure of the affected software until one is available. ## Is CVE-2019-1149 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-1149 exists. Public exploit code: - Microsoft Font Subsetting - DLL Heap Corruption in FixSbitSubTables (exploitdb) ## Other vulnerabilities in Microsoft Office - [CVE-2018-0798](https://insights.sbomify.com/CVE-2018-0798/): Microsoft Office Memory Corruption (high 8.8, exploited in the wild) - [CVE-2015-1770](https://insights.sbomify.com/CVE-2015-1770/): Microsoft Office Uninitialized Memory Use (high 8.8, exploited in the wild) - [CVE-2006-2492](https://insights.sbomify.com/CVE-2006-2492/): Microsoft Word Malformed Object Pointer (high 8.8, exploited in the wild) - [CVE-2018-0802](https://insights.sbomify.com/CVE-2018-0802/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild) - [CVE-2017-11882](https://insights.sbomify.com/CVE-2017-11882/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-1149 and fix it if it is affected. What it is: CVE-2019-1149 is a high-severity memory corruption vulnerability in Microsoft Office, published on 14 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-1149 exists. Affected product: Microsoft Office. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-1149/ (Markdown: https://insights.sbomify.com/CVE-2019-1149/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1149 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1149 - OSV: https://osv.dev/vulnerability/CVE-2019-1149 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-1149/ Summaries are generated and may contain mistakes; the official description above is the record.