Patch Gap in Chrome Could Have Been Weaponized by Attackers

Patch Gap in Chrome Could Have Been Weaponized by Attackers

1 Star2 Stars3 Stars4 Stars5 Stars (2 stemmen, gemiddelde: 5.00 uit 5)
Loading ...

Patch gapping is a serious issue that puts a system at risk of exploits. The problem stems from a gap in time before a patch of a security vulnerability in an open-source software is shipped to users.

The vulnerability may have been fixed already, or in the process of being fixed, and attackers can exploit the time before the patch arrives on users’ devices. This window, in which the knowledge of the vulnerability is semi-public while the user-base remains vulnerable, can range from days to months, explains security researcher István Kurucsai.

The Patch Gap in Google Chrome Explained

The researcher just discovered an instance of this issue in Google Chrome. The flaw could have been exploited in attacks against Chrome users days before the patch arrived.

It should be noted that not all patch gaps can be weaponized in attacks, and they are not that common. Niettemin, Kurucsai discovered one in Google Chrome’s v8 open-source component which is used as the browser’s JavaScript engine.

An interesting change list on chromium-review piqued our interest in mid-August. It was for an issue affecting sealed and frozen objects, including a regression test that triggered a segmentation fault. It has been abandoned (and deleted) since then in favor of a different patch approach, with work continuing under CL 1760976, which is a much more involved change, the researcher wrote in een blogpost.

Kort gezegd, the patch gap is due to the V8 issue which was patched in August. “Since the fix turned out to be so complex, the temporary solution for the 7.7 v8 branch was to disable the affected functionality. This will only be rolled into a stable release on the 10th of September,” de onderzoeker uitgelegd. Met andere woorden, the issue should now be closed with the release of Chrome 77.

Verwant: Onderzoekers Disclose Ongepatchte Android Zero-Day

According to the researcher and his team, attackers had plenty of time to weaponize this issue through the v8 changelog for security fixes. Even though the conception of a Chrome exploit is not an easy task, an attacker who is an expert in JavaScript could have done it. To prove his point, Kurucsai also released a PoC (proof-of-concept) on GitHUb. The PoC leverages the initial v8 problem to run malicious code in Chrome.

It should be noted that the PoC is not efficient enough as a second vulnerability to escape the Chrome sandbox is needed. Echter, attackers still could have utilized older Chrome sandbox escape flaws to leverage them with the patch gap issue.

Vorig jaar, researchers Karsten Nohl and Jakob Lell from security firm Security Research Labs uncovered a hidden patch gap in Android devices. De twee voerden een twee jaar durende analyse van 1,200 Android phones only to discover that most Android vendors regularly forget to include some patches, waardoor delen van het ecosysteem blootgesteld aan verschillende bedreigingen.


Milena Dimitrova

Een geïnspireerde schrijver en content manager die heeft met SensorsTechForum voor 4 jaar. Geniet ‘Mr. Robot’en angsten‘1984’. Gericht op de privacy van gebruikers en malware ontwikkeling, ze gelooft sterk in een wereld waar cybersecurity speelt een centrale rol. Als het gezond verstand heeft geen zin, ze zullen er zijn om aantekeningen te maken. Deze toelichtingen kunnen later om te zetten in artikelen!

Meer berichten

Laat een bericht achter

Uw e-mailadres wordt niet gepubliceerd. Verplichte velden zijn gemarkeerd *

Termijn is uitgeput. Laad CAPTCHA.

Delen op Facebook Aandeel
Loading ...
Delen op Twitter Gekwetter
Loading ...
Delen op Google Plus Aandeel
Loading ...
Delen op Linkedin Aandeel
Loading ...
Delen op Digg Aandeel
Deel op Reddit Aandeel
Loading ...
Delen op StumbleUpon Aandeel
Loading ...