4 ms·
> Next, let’s give ourselves an arbitrary write. To make the exploit a bit simpler, we’ll give ourselves an arbitrary memcpy. They took Signal-webrtc & added a
by jauntywundrkind 2y ago
> Next, let’s give ourselves an arbitrary write. To make the exploit a bit simpler, we’ll give ourselves an arbitrary memcpy.
They took Signal-webrtc & added a vulnerability to it.
Maybe maybe maybe there's some other means to exploit the lack of time check, but this feels like such a massive & overwhelmingly staked out nothing burger.
- BobbyTables2 2y agoI’m also surprised by this… They’re usually known for high quality research, not fluff like this…
- cwillu 2y ago“Now that we have 0-click parsing available, we need some vulnerabilities. As mentioned previously, we are not reporting any Signal 0-days in this post; the point of this series is a crash course in Signal, WebRTC, and iOS research. Let’s leverage Signal-WebRTC’s source code to inject our own vulnerability primitives and keep our research moving.”
- deleted 2y ago[deleted]