Re:CVE-2023-4863: Heap buffer overflow in WebP (Chrome)
by lifthrasiir on Wednesday September 13, 2023 @04:26AM
(#37493802)
MTE is good to have, but it only reduces the probability of successful attacks (by a factor of 16). If the process is allowed to segfault multiple times attackers have a good chance to work around MTE.
Re:CVE-2023-4863: Heap buffer overflow in WebP (Chrome)
by ignoramous on Thursday September 14, 2023 @06:50AM
(#37507280)
That's a general limitation with tagged pointers, I belive? Have you come across demonstrations of such exploits?
Re:CVE-2023-4863: Heap buffer overflow in WebP (Chrome)
by akyuu on Wednesday September 13, 2023 @05:54PM
(#37502254)
Do you have a source for that? AFAIK Pixel 7 uses an ARM v8.2 CPU, which doesn't support MTE. The upcoming Pixel 8 might support it, but Google hasn't announced anything yet.
Re:CVE-2023-4863: Heap buffer overflow in WebP (Chrome)
by ignoramous on Thursday September 14, 2023 @06:53AM
(#37507304)
I'm going by the bugreports I see for a FOSS app I develop: https://github.com/celzero/rethink-app/issues/962
See: https://source.android.com/docs/security/test/memory-safety/...
Google just did enable Memory Tagging Extension (ARM's hardware accelerated sanitizers) on the Pixels last year. May be sanitizing ISAs offer hope?