Monday, April 7, 2025
HomeChromeEmergency!! Hackers Actively Exploiting Chrome Zero-day Bug in Wide – Update Now

Emergency!! Hackers Actively Exploiting Chrome Zero-day Bug in Wide – Update Now

Published on

SIEM as a Service

Follow Us on Google News

This is an emergency notice for all Chrome users!!!

Google released an emergency update for Chrome that patches two new use-after-free vulnerabilities which include a zero-day bug that is actively exploiting in wide.

New stable channel update to Chrome 78.0.3904.87 released for Windows, Mac, and Linux.

- Advertisement - Google News

Researchers from Kaspersky discovered an unknown zero-day exploit for chrome browser and they called it as operation WizardOpiu.

Threat actors who behind this attack is unknown, but the code similarities indicate that the attack possibly linked with Lazarus group, an unknown team of hackers who are using Zero-days, spearphishing, malware, backdoors to attack various financial organization around the world.

The use-after-free vulnerability (tracked as CVE-2019-13720) affects the audio component of the web browser and the bug has been reported by Anton Ivanov and Alexey Kulaev at Kaspersky Labs.

Another use-after-free vulnerability has been uncovered as CVE-2019-13721 and fixed in this update which was reported by bug hunter bananapenguin. Google rewarded a bounty of $7,500.

The use-after-free vulnerability is a type of memory corruption flaw that allows an attacker to corrupt memory to escalates the privilege and take over the complete control of the vulnerable system by executing the arbitrary code remotely.

Exploiting the Chrome Zero-day

Researchers initial uncovered a malicious activity that leverages the waterhole type injection in the Korean site where the attacker inserted a weaponized javascript code on the main page.

The Javascript code load another remote script from the website hxxp://code.jquery.cdn.behindcorona[.]com and drops the anther script .charlie.XXXXXXXX.js that check the victim’s browser’s user agent to ensure that the system is vulnerable to infection and also it tries to extract the browser name and version.

“If the script found that the system browser is vulnerable then it tries to exploit the bug in Google Chrome browser and the script checks if the version is greater or equal to 65 “

Script checks the browser version

Later the malicious javascript establishes a connection to the remote server and downloads the bunches of chunks of the exploit code.

Once its all downloaded then the RC4 script decrypts the chunks where the attacker receives the new JavaScript code containing the full browser exploit. 

Downloaded browser exploit is completely obfuscated and the researchers de-obfuscate and uncovered that it has made another request against the user agent’s string and the second time it checks that the browser version is 76 or 77.

Researchers believe that “It could mean that the exploit authors have only worked on these versions (a previous exploitation stage checked for version number 65 or newer) or that other exploits have been used in the past for older Chrome versions.”

According to Kaspersky research ” The exploit used a race condition bug between two threads due to missing proper synchronization between them. It gives an attacker and a Use-After-Free (UaF) condition that is very dangerous because it can lead to code execution scenarios, which is exactly what happens in our case. “

Trigger the Use After Free Vulnerability

Once the exploit found the vulnerable victims, it immediately tries to trigger the UAF to perform an information leak about important 64-bit addresses.

It causes the following result to the attackers:

1) if an address is leaked successfully, it means the exploit is working correctly;
2) a leaked address is used to know where the heap/stack is located and that defeats the address space layout randomization (ASLR) technique;
3) a few other useful pointers for further exploitation could be located by searching near this address.

Along with this operation, it tries to perform various other processes such as allocate/free memory and bunches of other operations give the attackers to read/write an arbitrary code and take the complete control of the system.

The patch has already availed for all platforms such as Windows, Mac, and Linux. We recommend all the chrome users to immediately update the browsers and apply the patch to prevent this attack.

You can follow us on LinkedinTwitterFacebook for daily Cybersecurity and hacking news updates

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

Threat Actors Exploit Toll Payment Services in Widespread Hacking Campaign

In a sophisticated cybercrime operation, the Smishing Triad, a China-based group, has been identified...

Everest Ransomware Gang’s Leak Site Hacked and Defaced

TechCrunch has uncovered a concerning development in consumer-grade spyware: a stealthy Android monitoring app...

ToddyCat Attackers Exploited ESET Command Line Scanner Vulnerability to Conceal Their Tool

In a sophisticated cyberattack, the notorious ToddyCat APT group utilized a previously unknown vulnerability...

Threat Actors Use VPS Hosting Providers to Deliver Malware and Evade Detection

Cybercriminals are intensifying phishing campaigns to spread the Grandoreiro banking trojan, targeting users primarily...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Lazarus Adds New Malicious npm Using Hexadecimal String Encoding to Evade Detection Systems

North Korean state-sponsored threat actors associated with the Lazarus Group have intensified their Contagious...

New Credit Card Skimming Campaign Uses Browser Extensions to Steal Financial Data

A newly discovered credit card skimming campaign, dubbed "RolandSkimmer," is exploiting browser extensions to...

Mozilla Releases Urgent Patch for Windows After Chrome Zero-Day Exploit

Mozilla has released an urgent update for Firefox on Windows to address a critical...