Gap Patch Chrome aurait pu être militarisé par des attaquants
CYBER NOUVELLES

Gap Patch Chrome aurait pu être militarisé par des attaquants

1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, moyenne: 5.00 de 5)
Loading ...

bâillement Patch est un problème grave qui met un système à risque d'exploits. Le problème provient d'un décalage dans le temps avant qu'un correctif d'une vulnérabilité de sécurité dans un logiciel open-source est livré aux utilisateurs.




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. Cependant, 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 un billet de blog.

Peu dit, 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,” le chercheur a expliqué. En d'autres termes, the issue should now be closed with the release of Chrome 77.

en relation: Les chercheurs non corrigées Zero-Divulguer Day Android

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 (preuve de 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. Cependant, attackers still could have utilized older Chrome sandbox escape flaws to leverage them with the patch gap issue.

L'année dernière, researchers Karsten Nohl and Jakob Lell from security firm Security Research Labs uncovered a hidden patch gap in Android devices. Les deux ont effectué une analyse de deux ans 1,200 Android phones only to discover that most Android vendors regularly forget to include some patches, laissant les parties de l'écosystème exposés à diverses menaces.

avatar

Milena Dimitrova

Un écrivain inspiré et gestionnaire de contenu qui a été avec SensorsTechForum pour 4 ans. Bénéficie d' « M.. Robot » et les craintes de 1984 '. Axé sur la vie privée des utilisateurs et le développement des logiciels malveillants, elle croit fermement dans un monde où la cybersécurité joue un rôle central. Si le bon sens n'a pas de sens, elle sera là pour prendre des notes. Ces notes peuvent se tourner plus tard dans les articles!

Plus de messages

Laisser un commentaire

Votre adresse de messagerie ne sera pas publiée. Les champs obligatoires sont marqués *

Délai est épuisé. S'il vous plaît recharger CAPTCHA.

Partager sur Facebook Partager
Loading ...
Partager sur Twitter Tweet
Loading ...
Partager sur Google Plus Partager
Loading ...
Partager sur Linkedin Partager
Loading ...
Partager sur Digg Partager
Partager sur Reddit Partager
Loading ...
Partager sur Stumbleupon Partager
Loading ...