Zero click, silent, remote Android DoS

But imo it's not a bad thing. Most sites looked like shit in the past. The content is usually where I focus my changes when dealing with LLM generated HTML. And if I want it slightly less LLM flavored in terms of design I just pick a random design system to tell it to use. Apple HIG, IBM Carbon, etc.

Usually just picking your own palette, a design system, and making it remove all the stupid details it decides to add will improve your end result by a lot.

Also, I want to expunge the word "shape" from my vocabulary at this point. I think I'm developing a nerve twitch just reading it.

Or did I misunderstand you and can you input any phone number to cause this issue? If so that would sound more like a carrier issue then a android issue to me

Apk provided can be installed on an attackers phone, you specify the msisdn (phone number) of victims phone, click send and it crashes telephony app of the victim.

Multiple messages may create a race condition that corrupts an SQLite database that stores message which stops telephony from functioning as a phone. WiFi will still work so I guess you can use it as a tablet as long as you don’t mind the constant dialogs popping up.

Tested in AU, US, DE and UK with 100% success rate.

The author has provided an APK that claims to do just that. Hacking tools aren't allowed on app stores, no, but that has no bearing on the severity of vulnerabilities they exploit.

> And do any carriers actually let it go through their network and to a device like a normal message? It's entirely possible the malformed message would crash some software in the carrier's processing stack first and so never be delivered.

Apparently, unless you're accusing the author of lying.

> And if it doesn't, they could easily add a check to block such messages.

Your ISP could block RDP but that doesn't lessen the severity of RDP vulnerabilities, shift responsibility, or lessen the need for the vendor to respond in any way, that's not how this works.

This is an Android vulnerability and it should be assumed that the carrier is indifferent, actively hostile, cooperating with law enforcement to carry out this attack, or someone might carry out this attack using an IMSI catcher.

> It's difficult to believe they don't already have some sort of protection against spamming tons of messages to any device.

20? I doubt it. Do you think the author is lying?

> It's also entirely possible it works differently on different carriers, and some but not others might add blocks for this

Indeed. What's indefensible is Google's classification that this isn't a security vulnerability.

How do you make calls without trusting them?

The page describes that this part is resolved by putting the SIM into a non-Android device to receive the queued messages and acknowledge to the network.

To then recover the device it only vaguely mentions "adb commands" and "factory reset", but I can't find a description what actually needs to be done on the device.

I guess the specific question is: The message database that is corrupted due to this issue, is this DB owned by (and stored as part of) com.android.phone?

  *2767*3855#

That is a function of the training data/method, like many of AI's problems. This doesn't stop it being a problem of course, but it shouldn't be a surprise.

Big bugs, like heartbleed, over the years have had breathy websites going over how serious the problem is because the problem was that serious, so the models associate that sort of wording with bug reports. Less serious bugs don't get the same excited treatment, repeated in many many places, so more measured descriptions figure in the training data relatively less.

EDIT: actually already fixed in https://review.lineageos.org/c/LineageOS/android_frameworks_...

There's yet another PDU fixup that stems from negative index

That has more to do with the severity of heartbleed than the fact that it had a name and a logo. I've since seen a lot of vulnerabilities try to market themselves with websites, cute names, and stupid logos but I still don't remember them because they still just weren't big enough to actually be memorable.

A bit like the postal system. Yes, it's meant to send physical letters and what not to my home, but it still sucks when I get ads that just goes straight into the trash. Yes, you're using the system as intended, but I still consider your business slop if you send ads to me this way.

I used to write like this, but I can't anymore. (I suspect enough people did in the training set that that's why it ended up being part of the vernacular.)

I'm not familiar with WAP Push and how it works, but is it possible to disable it or block that port on a non-rooted phone?