CVE-2025-50165: Critical Flaw in Windows Graphics Component
None
<p>IntroductionIn May 2025, Zscaler ThreatLabz discovered CVE-2025-50165, a critical remote code execution (RCE) vulnerability with a CVSS score of 9.8 that impacts the Windows Graphics Component. The vulnerability lies within windowscodecs.dll, and any application that uses this library as a dependency is vulnerable to compromise, such as a Microsoft Office document. For example, attackers can exploit the vulnerability by creating a malicious JPEG image and inserting it into any file that leverages windowscodecs.dll. If a user opens that file, their system can be compromised by an attacker who can go on to perform RCE and take over the victim’s system.Microsoft released a patch to fix the vulnerability on August 12, 2025. Since the Windows Graphics Component is a critical part of all Windows systems, this vulnerability poses a significant security threat to every impacted Windows system. Affected VersionsThe following table outlines the specific Microsoft Windows products and versions impacted by CVE-2025-50165, and the corresponding patched versions that address the vulnerability:ProductImpacted VersionPatched VersionWindows Server 202510.0.26100.485110.0.26100.4946Windows 11 Version 24H2 for x64-based Systems10.0.26100.485110.0.26100.4946Windows 11 Version 24H2 for ARM64-based Systems10.0.26100.485110.0.26100.4946Windows Server 2025 (Server Core installation)10.0.26100.485110.0.26100.4946Table 1: Impacted Windows versions with vulnerable windowscodecs.dll and their patched versions.RecommendationsThreatLabz recommends Windows users update applications and install the patched versions specified in the affected versions table above.Attack ChainThe attack chain begins with a maliciously crafted JPEG image designed to exploit the vulnerability. This malicious image, when rendered via the windowscodecs.dll, will trigger the vulnerability. The exploit can also be triggered indirectly by embedding the image in another file such as a Microsoft Office document. When the exploit is triggered, the attacker can execute arbitrary code.How It WorksThis section references the methodology used by ThreatLabz to discover and analyze CVE-2025-50165. We touch on how ThreatLabz identified the vulnerable code path, the process of triaging the crash, and the development of a Proof-of-Concept (PoC) exploit.Identify the vulnerable path for fuzzingIn the figure below, line 51 served as the entry point for fuzzing. At this line, the original FileSize value can be replaced with MutatedBufferSize. This modification controls the buffer contents returned by MapViewOfFile and defines the snapshot’s entry point for subsequent fuzzing operations.Figure 1: IDA decompilation of the function GpReadOnlyMemoryStream::InitFile.Crash analysisThe fuzzing process successfully identified a crash, as shown in the figure below.Figure 2: Crash analysis of Microsoft Visio captured in WinDbg.The WinDbg output pinpointed the crashing instruction as call qword ptr [r8+10h] ds:0000080667c170=c0c0c0c0c0c0c0c0. This showed r8+10h was being dereferenced but pointed to uninitialized memory, a state identifiable by the c0c0c0c0c0c0c0c0 pattern used by Gflags. Further examination of the r8 register’s memory dump, shown in the figure below, revealed this uninitialized memory could be user-controlled through heap spraying.Figure 3: Memory dump of r8 register in WinDbg.The address 0000015fc1cab170 contained the untrusted function pointer. The pointer was dereferenced at the windowscodecs!jpeg_finish_compress+0xcc instruction, directly leading to the crash. To understand the execution flow that led to this point, ThreatLabz conducted a stack trace analysis, as illustrated below.STACK_TEXT:<br> RetAddr Call Site<br> 00007ffe`a8da58bb WindowsCodecs!jpeg_finish_compress+0xcc<br> 00007ffe`a8d4b6cd WindowsCodecs!CJpegTurboFrameEncode::HrWriteSource+0x46b<br> 00007ff7`16d6218b WindowsCodecs!CFrameEncodeBase::WriteSource+0x18dThe WinDbg stack trace highlighted three prominent functions within windowsCodecs.dll: jpeg_finish_compressCJpegTurboFrameEncode::HrWriteSourceCFrameEncodeBase::WriteSourceFurther investigation into the stack trace and additional research revealed the vulnerability’s precise origin and the corresponding code snippet. By modifying the path to the crafted JPEG file, the exact location of the vulnerability’s trigger was pinpointed to the execution of piFrameEncode->WriteSource, as shown in the example below. [ REDACTED ] // Create the decoder.<br> if (SUCCEEDED(hr))<br> {<br> hr = piFactory->CreateDecoderFromFilename(L”/path/to/poc.jpg”, NULL, GENERIC_READ,<br> WICDecodeMetadataCacheOnDemand, // For JPEG lossless decoding/encoding.<br> &piDecoder);<br> }<br> [ REDACTED ] if (SUCCEEDED(hr))<br> {<br> hr = piFrameEncode->WriteSource(<br> static_cast<iwicbitmapsource> (piFrameDecode),<br> NULL); // Using NULL enables JPEG lossless encoding.<br> }ExploitANALYST NOTE: Control Flow Guard (CFG) is disabled for the 32-bit version of windowscodecs.dll by default. However, the 64-bit version requires a CFG bypass to successfully exploit the vulnerability.By leveraging heap spraying and exploiting the untrusted pointer dereference vulnerability, control of the instruction pointer (IP) can be obtained which enables further exploitation through Return-Oriented Programming (ROP). This is achieved with the following steps:Allocate a series of heap chunks, each sized 0x3ef7, with the ROP chain data stored within them.Free some of these heap chunks and return them to the free list so that one is reallocated as the victim chunk.Trigger the untrusted pointer dereference vulnerability.Use RIP control to employ a stack pivot gadget and redirect execution to the ROP chain stored within the heap.The figure below shows the exploitation process and the resulting crash output.Figure 4: Illustration of the exploitation steps and the resulting crash output captured in WinDbg.With control of the IP established through the exploitation process, the next phase involves leveraging ROP gadgets to achieve arbitrary code execution. These gadgets are used to create a Read-Write-Execute (RWX) memory region using a function like VirtualAlloc. Once the RWX memory is set up, additional ROP gadgets such as mov dword [rax], rcx, where RAX points to the shellcode address and RCX contains the shellcode data, are used to write the malicious shellcode into this newly created memory region. Finally, execution is redirected to the shellcode by jumping to the address of the RWX memory.Proof-of-Concept (PoC)To demonstrate the exploitation of the vulnerability, ThreatLabz created an example application which allows the user to control the heap and process the JPEG image using the three functions. Enables the creation of heap allocations with user-specified inputs:Index: Specifies the location in a global array where the allocated heap address will be stored (e.g., index 0, 1, …).Size: Determines the size of the heap memory block to allocate.Data: Represents the value stored within the allocated memory block.Frees a heap allocation based on the provided index value.Accepts Base64-encoded JPEG image data and uses the JPEG re-encode example code to process the image.Terminates the application.In the figure below, the memory address 0X00007FF7F0BB448, displayed as Reward, represents the virtual memory address of the application’s main function. This address allows users to calculate the base address where the application’s process is mapped in memory, providing critical information for exploitation. Using options 1 and 2, users can perform a heap spray attack by densely allocating and freeing heap memory chunks to control the layout of data in memory. Option 3 then triggers the vulnerability by processing a specially crafted JPEG image, leveraging the heap spray setup to manipulate the application’s control flow and gain access to memory required for exploitation.Figure 5: Core functionality of the executable used to demonstrate the PoC.Check out this video for a detailed demonstration of RIP control in the example application, showing how RCE is achieved during the exploitation process.</iwicbitmapsource><br> ConclusionWith a CVSS score of 9.8, CVE-2025-50165 poses a significant risk to all Windows environments as the Microsoft Graphics Component is integral to all Windows environments. It is critical that Windows users update applications and install the patched versions in a timely manner.Zscaler CoverageThe Zscaler ThreatLabz team has deployed protection for CVE-2025-50165.</p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2025/11/cve-2025-50165-critical-flaw-in-windows-graphics-component/" data-a2a-title="CVE-2025-50165: Critical Flaw in Windows Graphics Component"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2025%2F11%2Fcve-2025-50165-critical-flaw-in-windows-graphics-component%2F&linkname=CVE-2025-50165%3A%20Critical%20Flaw%20in%20Windows%20Graphics%20Component" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2025%2F11%2Fcve-2025-50165-critical-flaw-in-windows-graphics-component%2F&linkname=CVE-2025-50165%3A%20Critical%20Flaw%20in%20Windows%20Graphics%20Component" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2025%2F11%2Fcve-2025-50165-critical-flaw-in-windows-graphics-component%2F&linkname=CVE-2025-50165%3A%20Critical%20Flaw%20in%20Windows%20Graphics%20Component" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2025%2F11%2Fcve-2025-50165-critical-flaw-in-windows-graphics-component%2F&linkname=CVE-2025-50165%3A%20Critical%20Flaw%20in%20Windows%20Graphics%20Component" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2025%2F11%2Fcve-2025-50165-critical-flaw-in-windows-graphics-component%2F&linkname=CVE-2025-50165%3A%20Critical%20Flaw%20in%20Windows%20Graphics%20Component" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://www.zscaler.com/blogs/feeds/security-research">Security Research | Blog</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by ThreatLabz (Zscaler)">ThreatLabz (Zscaler)</a>. Read the original post at: <a href="https://www.zscaler.com/blogs/security-research/cve-2025-50165-critical-flaw-windows-graphics-component">https://www.zscaler.com/blogs/security-research/cve-2025-50165-critical-flaw-windows-graphics-component</a> </p>