irresponsible disclosure aficionado

The Netherlands
Joined April 2009
man, @officialmcafee would’ve been so psyched for the entire world finally latching onto PHP (until he would discover they are talking about some nerd shit and not grade-a alpha-pyrrolidinohexanophenone)
1
1
18
1,094
blasty retweeted
OpenAI independently reported the same root cause ON THE SAME DAY? I hope that it is just a coincidence...
From the PHP Foundation on who found it first 👇
2
1
17
1,058
SHELLSHOCK II: ELECTRIC BUG-ALOO ?
2
8
1,546
tl;dr: responsible/coordinated disclosure is cooked && you cannot argue with a (root)shell
For the next few months, we are looking at frequent discoveries of long-standing bugs - competent code auditing has gotten cheap and abundant. This carries a few consequences:
1
16
1,840
anthropic has employees installing mics in their own offices.. openAI had some questionable situation with the navier stokes discovery. we need to stop sending them good context.. .. although most collisions are probably just people rolling the virtual dice in a similar way ;)
There is a recurring info I hear from vendors that there is often a first discovery of a vulnerability by AI and suddenly one or two weeks later lots of collisions come in. In this case the PHP bugs were first discovered 5th August and then rediscovered 2 weeks later
1
6
2,024
vulnerability vultures are everywhere ;-(
The amount of scavengers that come out just as a new vulnerability is disclosed is insane in the age of AI...
2
1
22
1,355
cube.obj with fire.glsl shader :O #TheSAS2026
15
1,128
had some time to kill en route to #TheSAS2026 dinner party.. so clanked on php apocalypse PoC.. ;-PPpppPp
6
7
63
6,873
yes, on a fucking iphone
1
14
892
💯💯
this is such an insane thing to admit. imagine the security of your network is based on the outputs of dozens of independent dumb llms that no person will be able to understand or safely extend in the future
11
1,573
keep your signers air- and signal-gapped bro
10
1,167
so what's the proper mitigation for a ledger style hw supplychain attack? tiny LCD screens with encrypted SPI bus ? :-P you cannot *really* defend against any of this, of course. while this is a pretty obvious bug and not some bloomberg-rice-grain-sized-implant; expecting endusers to take apart their devices and visually inspect the PCBs is about as bad as UX can get. but more importantly it could also provide a false sense of security. what if there's a less obvious implant? some backdoored uC/secure element ICs, would you be able to spot them?! 👻
7
1
9
2,279