← Back to context Comment by d2kx 7 hours ago This issue is already fixed in Google Chrome (152.0.7977.83) 2 comments d2kx Reply azakai 6 hours ago TFA says> Type confusion in V8 in Google Chrome prior to 152.0.7977.82 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page.So it was fixed in 152.0.7977.82 (before .83), if I read that right. ttsiodras 18 minutes ago You read that right. From the article:"Affected products: ... Up to (excluding) 152.0.7977.82".82 is fixed.
azakai 6 hours ago TFA says> Type confusion in V8 in Google Chrome prior to 152.0.7977.82 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page.So it was fixed in 152.0.7977.82 (before .83), if I read that right. ttsiodras 18 minutes ago You read that right. From the article:"Affected products: ... Up to (excluding) 152.0.7977.82".82 is fixed.
ttsiodras 18 minutes ago You read that right. From the article:"Affected products: ... Up to (excluding) 152.0.7977.82".82 is fixed.
TFA says
> Type confusion in V8 in Google Chrome prior to 152.0.7977.82 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page.
So it was fixed in 152.0.7977.82 (before .83), if I read that right.
You read that right. From the article:
"Affected products: ... Up to (excluding) 152.0.7977.82"
.82 is fixed.