Conversation

CONFIRMED: Android 5 is vulnerable to #SMSofDeath. It repeatedly restarts com.android.phone and shows "process has crashed" dialog windows immediately one after another. Doesn't bootloop, but may hang the system a couple of seconds after a reboot.

Clearing data of "telephony provider" via adb shell didn't work, i had to do a factory reset.

1
1
0

For context:

  • the ai-generated landing smsofdeath.com states that affected Android versions are 12 to 17,
  • but git blame on the vulnerable code clearly shows that last time it was changed was in 2013, and then git-blaming same file from the parent commit leads to a 2012 commit initially creating frameworks/opt/telephony.

I've just proved experimentally that the latter is true and the vulnerability has always been reachable.

1
0
0

Here's the commit that introduced the NegativeArraySize crash, it's from 2009, a couple of months younger than me.

Before that commit, apparently, Android would just allocate a 2 gigabyte buffer neocat_3c

int headerLength = (int)pduDecoder.getValue32();
int dataIndex = headerStartIndex + headerLength;
byte[] data = new byte[pdu.length - dataIndex];
1
0
0

@darkcat09 > Android would just allocate a 2 gigabyte buffer

No, that is not even remotely possible on devices of that era. I say this as someone with multiple devices from early Android history, including the first one.

2
0
0

@darkcat09 yes, android would oomkill that instantly

0
0
0
@hexaheximal @darkcat09 does android not have overcommit enabled?
1
0
0