[HN Gopher] A 0-click exploit chain for the Pixel 9 Part 1: Deco...
___________________________________________________________________
A 0-click exploit chain for the Pixel 9 Part 1: Decoding Dolby
Author : el_duderino
Score : 26 points
Date : 2026-01-15 17:28 UTC (5 hours ago)
(HTM) web link (projectzero.google)
(TXT) w3m dump (projectzero.google)
| amatecha wrote:
| > The UDC is integrated into a variety of hardware and platforms,
| including Android, iOS, Windows and media streaming devices. It
| is shipped to most OEMs as a binary 'blob' with limited symbols,
| which is then statically linked into a shared library.
|
| Does that suggest this is a vulnerability on other platforms as
| well?
| ronsor wrote:
| The article claims iOS/macOS is likely not vulnerable. I'm not
| sure about Windows.
| adrian_b wrote:
| It should be noted that iOS/macOS is likely to be not
| vulnerable because for them the Dolby decoder has been
| compiled as any C/C++ program should be compiled by default
| everywhere, i.e. with bounds checking enabled.
|
| Unfortunately, all C/C++ compilers have as the default option
| to omit bounds checking, but any decent compiler has options
| for enabling bounds checking and other run-time checks
| suitable for catching all the undesirable behaviors that are
| undefined in the C/C++ standards. The default should be to
| enable such options globally for any program and to disable
| them selectively only for the code parts where benchmarks
| have demonstrated that they prevent the program to reach the
| target performance and code analysis has concluded that the
| erroneous behavior cannot happen.
___________________________________________________________________
(page generated 2026-01-15 23:01 UTC)