# CVE-2019-1043: Comctl32 Remote Code Execution Vulnerability > Remote code execution via memory corruption in comctl32.dll allows attackers to take control of systems when users visit malicious websites. - **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 12 Jun 2019 - **Updated:** 20 May 2025 - **Also known as:** GHSA-jv5f-3fwg-6pqw ## What is CVE-2019-1043? CVE-2019-1043 is a medium-severity memory corruption vulnerability in Microsoft Windows 10, published on 12 Jun 2019. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. ### Official description A remote code execution vulnerability exists in the way that comctl32.dll handles objects in memory. The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, the attacker could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. An attacker could host a specially crafted website designed to exploit the vulnerability through Internet Explorer and then convince a user to view the website. The attacker could also take advantage of compromised websites, or websites that accept or host user-provided content or advertisements, by adding specially crafted content that could exploit the vulnerability. However, in all cases an attacker would have no way to force a user to view the attacker-controlled content. Instead, an attacker would have to convince a user to take action, typically by an enticement in an email or instant message, or by getting the user to open an attachment sent through email. The security update addresses the vulnerability by modifying how comctl32.dll handles objects in memory. ## Which versions are affected by CVE-2019-1043? It affects 8 products. Products: 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-1043? No fix has been published for CVE-2019-1043 yet. Limit exposure of the affected software until one is available. ## Is CVE-2019-1043 being exploited? There is no known exploitation of CVE-2019-1043 in the wild and no public exploit code. ## Other vulnerabilities in Microsoft Windows 10 - [CVE-2015-2426](https://insights.sbomify.com/CVE-2015-2426/): Microsoft Windows Adobe Type Manager Library Remote Code Execution (high 8.8, exploited in the wild) - [CVE-2015-1769](https://insights.sbomify.com/CVE-2015-1769/): Microsoft Windows Mount Manager Privilege Escalation (medium 6.6, exploited in the wild) - [CVE-2020-1467](https://insights.sbomify.com/CVE-2020-1467/): Windows Hard Link Elevation of Privilege Vulnerability (critical 10.0) - [CVE-2021-26424](https://insights.sbomify.com/CVE-2021-26424/): Windows TCP/IP Remote Code Execution Vulnerability (critical 9.9) - [CVE-2021-28476](https://insights.sbomify.com/CVE-2021-28476/): Windows Hyper-V Remote Code Execution Vulnerability (critical 9.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-1043 and fix it if it is affected. What it is: CVE-2019-1043 is a medium-severity memory corruption vulnerability in Microsoft Windows 10, published on 12 Jun 2019. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-1043 in the wild and no public exploit code. Affected product: Microsoft Windows 10. 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-1043/ (Markdown: https://insights.sbomify.com/CVE-2019-1043/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1043 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1043 - OSV: https://osv.dev/vulnerability/CVE-2019-1043 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-1043/ Summaries are generated and may contain mistakes; the official description above is the record.