Tuesday, December 3, 2024
HomeComputer SecurityAnonymous Hacker Leaked Another 2 Windows Zero-day Exploit in GitHub

Anonymous Hacker Leaked Another 2 Windows Zero-day Exploit in GitHub

Published on

SIEM as a Service

SanboxEscaper, an anonymous hacker, exploit writer leaked two more Windows zero-day bug in Github along with exploit code.

Yesterday, she published a 5th Zero-day bug (1, 2, 3, 4, 5 ) that resides in Windows Task Scheduler let attackers perform a local privilege escalation (LPE) and gain complete control of fully patched current version of Windows 10.

Today there are two more new zero-days that she leaked with exploits code, which is an Internet Explorer 11 SandboxEscape and the another zero-day marked as “InstallerBypass.”

- Advertisement - SIEM as a Service

IE 11 SandboxEscape Zero-day

Internet Explorer 11 sandbox escape zero-day allows attackers to inject the malicious code into the sandboxed iexplore.exe and bypass the protection mode.

SanboxEscaper released a video as a guide where the bug has been demonstrated using her exploit code.

Zero-day Exploit that released by SanboxEscaper will trigger the vulnerability in IE 11 by injecting malicious DLL in a specific process (iexplore.exe).

Once the exploit successfully exploited, it allows the opening of windows filepickers through a broker and the IL javascript execution.

At this point, The zero-day trigger the IE RCE to bypass the protection mode and disable it. You can see this process in the above video, where she demonstrates with her exploit code.

InstallerBypass Zero-day

The installer bypass vulnerability can be triggered by capturing the rollback scripts, and to inject the files through Windows Installer “msiexec.” The timing to execute the PoC is minimal, it needs to be demonstrated before it writes the Discretionary Access Control List.

SandboxEscaper created an executable, polarbear[.]exe, when the executable is triggered through windows the installer or msiexec and if the repair flag passed along with installation, you get some additional time to trigger the vulnerability.ability.

If the PoC execution is successful, then it writes oops.dll into the system32 folder. SandboxEscaper said. See the demo video below.

Attackers can trigger the vulnerability to deploy the malware by passing the silent flag to hide installer UI and to run the process in background.

Also SandboxEscaper posted a statement in her blogspot says,

There’s two more bugs on github

“F*ck this shitty industry. I don’t plan to make a career in it anyway.”

“I hate all the people involved in this industry.”

“Everyone just thinks they know better. Everyone just loves pointing fingers. Bunch of apes.”

You can follow us on Linkedin, Twitter, Facebook for daily Cybersecurity updates also you can take the Best Cybersecurity courses online to keep your self-updated.

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

PEFT-As-An-Attack, Jailbreaking Language Models For Malicious Prompts

Federated Parameter-Efficient Fine-Tuning (FedPEFT) is a technique that combines parameter-efficient fine-tuning (PEFT) with federated...

Hackers Cloning Websites, Exploiting RCE Flaws To Gain Access To Shopping Platforms

Cybercriminals are leveraging AI-powered phishing attacks, website cloning tools, and RCE exploits to target...

Hackers Exploited Windows Event Logs Tool log Manipulation, And Data Exfiltration

wevtutil.exe, a Windows Event Log management tool, can be abused for LOLBAS attacks. By...

Threat Actors Allegedly Claims Breach of EazyDiner Reservation Platform

Reports have emerged of a potential data breach involving EazyDiner, a leading restaurant reservation...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

Salesforce Applications Vulnerability Could Allow Full Account Takeover

A critical vulnerability has been discovered in Salesforce applications that could potentially allow a...

TP-Link HomeShield Function Vulnerability Let Attackers Inject Malicious Commands

A significant vulnerability has been identified in TP-Link's HomeShield function, affecting a range of...

HPE IceWall Flaw Let Attackers cause Unauthorized Data Modification

Hewlett Packard Enterprise (HPE) has issued an urgent security bulletin addressing a critical vulnerability...