零交互且阻断紧急呼叫,覆盖面为整条 Android 机型线
移动端dospoc
RT @ptdbugs: SMS of Death: Zero-Click Android Telephony DoS via WAP Push
Read on dbugs: https://t.co/GE7F4hH64x
A researcher has published an analysis of a vulnerability in the Android telephony stack that allows an attacker to remotely disable a phone with a single text message. The attack is zero-click: it requires no interaction from the victim and causes a persistent denial of service, including preventing the victim from calling emergency services.
What’s the issue?
The flaw is located in the "WapPushOverSms.decodeWapPdu()" method in the "frameworks/opt/telephony" system component. The WSP header is parsed as a "uintvar", returned as a "long", then cast to "int" without range checking and used directly as the size of a new array:
│ // https://t.co/YbnrbSPLH2
│ int headerLength = (int) pduDecoder.getValue32();
│ // https://t.co/xLHo5VJITX
│ byte[] header = new byte[headerLength];
The five-byte value "88 80 80 80 00" decodes to "0x80000000". When cast to a signed 32-bit integer, it becomes "-2147483648". Allocating an array with a negative length throws an uncaught "NegativeArraySizeException", crashing the main telephony thread.
Attack mechanics
• Delivery vector. The message is delivered as a data SMS via WAP Push to port 2948. It does not appear in Messages, the sender’s number is not displayed, and no notifications are shown.
• Immediate effect. The "https://t.co/QWrt3u4DYv" process crashes, active calls are dropped, telephony service becomes unavailable for 1–2 seconds, and the process then restarts.
• Carrier redelivery. If the message is not acknowledged, the carrier resends it, causing the phone to crash again. In testing, a single message triggered recurring outages for up to a week.
• Boot loop. The malformed message remains queued in "content://sms/raw" and is reprocessed on every boot. Android RescueParty reboots the device into recovery mode approximately every 90 seconds, eventually prompting the user to perform a factory reset.
Impact on emergency calls
While the device is under attack or stuck in a reboot loop, it cannot reliably place emergency calls. The attack may not only disrupt the phone’s operation but also result in the carrier blocking the device until the issue is resolved. For example, in Australia, access to the 000 emergency number is a mandatory feature of mobile service. Carriers are required to identify phones that cannot connect to emergency services and may disconnect affected devices from the network.
Article: https://t.co/GgEi0S7iIC