Exploiting Android Messengers with WebRTC: Part 2
Summary: Project Zero's Natalie Silvanovich, in Part 2 of a three-part series published August 5, 2020, found CVE-2020-6514, a WebRTC bug that sends the memory location of the SctpTransport object to the remote peer during every SCTP connection, and a use-after-free in usrsctp's ASCONF chunk handling (Bug 376, reported by Mark Wodrich on September 19, 2019) that she chained to make a target device send back its own memory. She also found CVE-2020-6831, a stack buffer overflow in usrsctp that gives an attacker complete control of the overflow's size and contents but is not reachable through WebRTC because both sockets are client sockets.
Bottom line: The exploit's reliability hinges on ASLR layout, which on Android is fixed at device startup and does not change until reboot, so a failed attempt tends to fail repeatedly on the same device - and the fix depended on applications applying WebRTC patches, which the series says they often do not.
Read the original at Google Project Zero ↗
- Topics
- Vulnerabilities & Patching
- Mentions
- CVE-2020-6514CVE-2020-6831
- Related
- Exploiting Android Messengers with WebRTC: Part 3 Cyber Risks ·Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026