Design Weakness in Microsoft CFG Allows Complete Bypass

  /     /     /  
Publicated : 22/11/2024   Category : security


Design Weakness in Microsoft CFG Allows Complete Bypass


Researchers from Italys University of Padua will demo a new technique to evade Control Flow Guard, the widely deployed security mechanism, at Black Hat Asia.



A widely deployed security mechanism in Windows that is designed to prevent attackers from exploiting memory corruption errors can be completely bypassed because of a fundamental design weakness, according to researchers from the University of Padua, in Italy.
In a talk at the upcoming Black Hat Asia conference in Singapore later this month, the researchers plan to show how attackers can exploit the design weakness to execute code of their choice running in the applications context.
The design flaw exists in Control Flow Guard (CFG), a mechanism that Microsoft has implemented in all Windows operating systems from Windows 8.1 to the latest version of Windows 10. CFG, like Microsofts Address Space Randomization Layer (ASLR), is one of several countermeasures that have been deployed in recent years to protect against exploits targeting memory corruption vulnerabilities in software. More than 500 million Windows systems have the feature currently.
As the researchers from the University of Padua explain in a technical paper describing their exploit, CFG is designed to prevent attackers from hijacking a programs control flow and directing it toward their own malicious code. The mechanism works by ensuring the order in which a program executes functions — or its control flow — follows specific valid paths.
CFG restricts indirect calls or jumps — for example, via function pointers — to an allowed target set determined at compile time, says Andrea Biondo, a computer science student at the University of Padua. So, an attacker cant just hijack execution to arbitrary locations.
But some trade-offs Microsoft made in CFG to accommodate performance and backward compatibility requirements have created an opening for attackers. The CFG design vulnerability gives attackers a way to call portions of code — or gadgets — that should not be allowed and that can be chained together to bypass CFG restrictions entirely, according to the paper.
The [control flow] restriction is precise only when the allowed targets are aligned to 16 bytes, Biondo says. If they are not, then there is a 16-byte imprecision around the target that attackers can take advantage of to bypass CFG, he notes.
An evaluation of Windows system libraries uncovered many exploitable gadgets in code loaded by almost all Windows applications on 32-bit systems and Web browsers on 64-bit systems, they said. By combining the presence of unaligned targets in common libraries with the predictability of the layout of functions generated by the compiler, we can bypass CFG, Biondi says.
A 16-byte imprecision might not look like the end of the world at first sight, he adds. However, it is actually very significant since the compiler leaves so many unaligned targets around.
The researchers have dubbed their exploit as the Back to the Epilogue (BATE) attack and have described it as a generic bypass for Microsofts Control Flow Guard. The proof-of-concept code that the researchers plan to present at Black Hat applies BATE on Microsofts Edge browser on Windows 10 (64-bit), Biondo says. The Edge vulnerabilities used are long known, and the goal is purely to demonstrate that BATE can be exploited in real-world attacks.
According to Biondo, BATE is different from other flow integrity bypass techniques such as Endgames
Counterfeit Object-Oriented Programming
(COOP) from last August.
With those, you need to write your whole payload — or at least, a first stage — with a restricted gadget, which makes it harder, he says.
BATE just bypasses CFG completely, so an attacker can then apply more common and easier code-reuse techniques for the payload. Previous bypasses were more application-specific, while BATE requires only certain common libraries to be loaded by the victim process. On 32-bit, basically everything is exploitable because the C runtime library is exposed to BATE, Biondo says.
To the best of our knowledge, Microsoft is going to fix this in the RS4 Windows update, he adds.
Related content:
Researcher Finds Hole in Windows ASLR Security Defense
Microsoft Patches Exploited Office Bug
Microsoft: How the Threat Landscape Will Shift This Year
Best of Black Hat: 20 Epic Talks in 20 Years
 
 
Black Hat Asia returns to Singapore with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier solutions and service providers in the Business Hall. Click for information on the
conference
 and
to register.

Last News

▸ Veritabile Defecte de Proiectare a Securitatii in Software -> Top 10 Software Security Design Flaws ◂
Discovered: 23/12/2024
Category: security

▸ Sony, XBox Targeted by DDoS Attacks, Hacktivist Threats ◂
Discovered: 23/12/2024
Category: security

▸ There are plenty of online tools for reporting bugs. ◂
Discovered: 23/12/2024
Category: security


Cyber Security Categories
Google Dorks Database
Exploits Vulnerability
Exploit Shellcodes

CVE List
Tools/Apps
News/Aarticles

Phishing Database
Deepfake Detection
Trends/Statistics & Live Infos



Tags:
Design Weakness in Microsoft CFG Allows Complete Bypass