@leocg: Yes that sounds cool. So tell me, where are the backport entries for the 9 missing high and critical security fixes that appeared with the subsequent Chromium versions (including two 0-days with active expoilts in the wild) in the changelog? Or was your answer just to draw attention away from Opera letting their users down?
Best posts made by antonio1678
-
RE: Opera 110Blogs
-
RE: Opera 99.0.4788.13 Stable updateBlogs
Ok I will give you that one, finally you did a fast turn around!
-
RE: Opera 110Blogs
@adam1709: CVE-2024-4671 is so last week. There is a new zero day as of late yesterday. CVE-2024-4761. Yes look carefully at that number it is different https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_13.html
It seems like so far only Chrome and Vivaldi have the fix for that one.
-
RE: Opera 110Blogs
@adam1709: Now they have another to catch up on. There is yet another 0-day annouced today: CVE-2024-4947: Type Confusion in V8
-
RE: Opera introduces Lucid Mode to improve video qualityBlogs
Cool and with all the other Chromium browsers on 108 and you stuck on 107.0.5304.122. Are you going to release a security fix for CVE-2022-4262, you know the zero day from 12 DAYS AGO!??
P.S. There were 8 more fixes in 108.0.5359.124 released yesterday. I also wonder how many of those affect you:
https://chromereleases.googleblog.com/search/label/Desktop Update -
RE: Opera 110Blogs
@leocg: I notice you hand waved past the answer that was required, choosing only to talk about Chromium versions varying between browsers. I'll go straight to the point, are the security fixes found in the latest Chrome here or not?
-
RE: Opera 110Blogs
@kmielczarczyk: Which of the two 0-days since the .61 release would that be, given there is no CVE listed in the change log (please fix that) and these have been two separate 0-days? Is it "High CVE-2024-4671: Use after free in Visuals"? Ok, then how about the other 0-day, "High CVE-2024-4761: Out of bounds write in V8"? Is that also fixed and you forgot to list it? And what about all of these security fixes that are not listed in your change log? Do you have them as well? Why would you back port these when you could just move up the Chromium branch and get them all more easily than needing to back port?
High CVE-2024-4558: Use after free in ANGLE
High CVE-2024-4559: Heap buffer overflow in WebAudio
High CVE-2024-4331: Use after free in Picture In Picture
High CVE-2024-4368: Use after free in Dawn
Critical CVE-2024-4058: Type Confusion in ANGLE
High CVE-2024-4059: Out of bounds read in V8 API
High CVE-2024-4060: Use after free in DawnI don't want to call you a liar but what you are saying makes little sense and hence I am struggling to believe it. Nonetheless, if you have fixes for all of these… please update the change log.