CVE-2016-0038 Memory corruption in n/a
Remote attackers can execute arbitrary code by tricking users into opening a crafted Journal file in Microsoft Windows.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2016-0038?
CVE-2016-0038 is a high-severity memory corruption vulnerability in Microsoft Windows 10, published on 10 Feb 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
Windows Journal in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, and Windows 10 Gold and 1511 allows remote attackers to execute arbitrary code via a crafted Journal file, aka "Windows Journal Memory Corruption Vulnerability."
Weakness: CWE-119
Which versions are affected by CVE-2016-0038?
It affects 6 products.
Products include Microsoft Windows 10, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista.
How do I fix CVE-2016-0038?
No fix has been published for CVE-2016-0038 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2016-0038 being exploited?
There is no known exploitation of CVE-2016-0038 in the wild and no public exploit code.
Other vulnerabilities in Microsoft Windows 10
- CVE-2015-2426 Microsoft Windows Adobe Type Manager Library Remote Code Execution
- CVE-2015-1769 Microsoft Windows Mount Manager Privilege Escalation
- CVE-2020-1467 Windows Hard Link Elevation of Privilege Vulnerability
- CVE-2021-26424 Windows TCP/IP Remote Code Execution Vulnerability
- CVE-2021-28476 Windows Hyper-V Remote Code Execution Vulnerability
Sources
Also known as GHSA-26v4-vq66-h2r9.