How most vulnerabilities are explained:
–There’s a big security problem with XY.
–Really? What is it?
–Well, you know how X works?
–Yeah.
–And you know how Y works?
–Yes.
–…
–Oh…
I'm looking for a quote about bug class discovery (iirc a tweet by @dakami)
It goes something like this:
Q: Do you know how A works?
A: Yes
Q: Do you know how B works?
A: Yes
Q: How do you think these things interact?
A: Oh shit!
I'd like to cite it.(cc @maradydd@sergeybratus)
Cloud computing is about everybody making the same (and individually quite safe) bet against total systems collapse.
Thank goodness large parts of it aren't owned by a crazy space billionaire.
Hot-take: Elon buying twitter was all about stress-testing his new dumpster-fire rocket engines, and apparently investor money has a very high specific impulse.
@dreadpir8robots The binary (x86-64) shellcode does chmod("/bin/chmod",0755);exit(?);, EB FC are jumps that hop backward into this shellcode, this gets sprayed all over the VDSO calls' entry points.
@swagitda_ Not sure I agree with the difficult-to-scale part. It seems to me that for an attacker it's a high upfront cost to permanently* solve a stage in many different multi-staged attacks. (* assuming no mitigation)
@Kxyne@thegrugq@netspooky@securityfreax It used to work with /proc/<pid>/stat https://t.co/csO3qCuHTw . Looks like /proc/<pid>/syscall needs root though.