4 ms·

Zerodium say they have nothing to do with this: https://twitter.com/cBekrar/status/1376469666084757506 https://twitter.com/cBekrar/status/1376469666084757506

tester34 6y ago
>Likely, the researcher(s) who found this bug/exploit tried to sell it to many entities but none wanted to buy this crap but why so snarky?
- pas 6y ago
  twitter. the takes are hotter than the sun, the style is snarkier than zkSNARKs.
mvolfik 6y ago
am I understanding it correctly that somebody had breached the PHP git server and tried selling it to 0-day and similar exploiting businesses?
- Sebb767 6y ago
  That was my assumption given that they explicitly mentioned zerodium. But so far only the commit itself is public, so until we know more about the attack or the attacker, this is pure speculation. The tweet from zerodium is not clear on whether they received an offer for this vulnerability, unfortunately.
lawl 6y ago
> Zerodium say they have nothing to do with this Would they admit if they did?
- fernandotakai 6y ago
  "zerodium investigated zerodium and zerodium found out that zerodium had nothing to do with this"
  - kuroguro 6y ago
    Well the opposite may be true too - the comment may be lying about it having anything to do with zerodium or that date. Could be just a meme or a bad attempt of misdirection in case it went undetected for a while.
- Sebb767 6y ago
  That's unknown, but it would be strange for them to be involved - it would not make much sense for them to pay out a bounty to themselves. I think it's far more likely that someone tried to plant this there in order to cash out via zerodium.
tutfbhuf 6y ago
Maybe the person that reported the exploit to Zerodium already cashed out in mid 2017 and was angry that the exploit hasn't been fixed yet. Therefore, he decided to make it very obvious and force php to react.
- Angius 6y ago
  I believe the exploit itself was introduced with the commit in question, it wasn't there before.
  - kenmacd 6y ago
    The other exploit, the one that allowed the commit to be injected.
  - toxik 6y ago
    As has been pointed out elsewhere, the exploit is the ability to inject code into the PHP Git repository. Not this RCE.

tester34 6y ago

>Likely, the researcher(s) who found this bug/exploit tried to sell it to many entities but none wanted to buy this crap but why so snarky?

pas 6y ago
twitter. the takes are hotter than the sun, the style is snarkier than zkSNARKs.

mvolfik 6y ago

am I understanding it correctly that somebody had breached the PHP git server and tried selling it to 0-day and similar exploiting businesses?

Sebb767 6y ago
That was my assumption given that they explicitly mentioned zerodium. But so far only the commit itself is public, so until we know more about the attack or the attacker, this is pure speculation. The tweet from zerodium is not clear on whether they received an offer for this vulnerability, unfortunately.

lawl 6y ago

> Zerodium say they have nothing to do with this Would they admit if they did?

fernandotakai 6y ago
"zerodium investigated zerodium and zerodium found out that zerodium had nothing to do with this"
- kuroguro 6y ago
  Well the opposite may be true too - the comment may be lying about it having anything to do with zerodium or that date. Could be just a meme or a bad attempt of misdirection in case it went undetected for a while.
Sebb767 6y ago
That's unknown, but it would be strange for them to be involved - it would not make much sense for them to pay out a bounty to themselves. I think it's far more likely that someone tried to plant this there in order to cash out via zerodium.

tutfbhuf 6y ago

Maybe the person that reported the exploit to Zerodium already cashed out in mid 2017 and was angry that the exploit hasn't been fixed yet. Therefore, he decided to make it very obvious and force php to react.

Angius 6y ago
I believe the exploit itself was introduced with the commit in question, it wasn't there before.
- kenmacd 6y ago
  The other exploit, the one that allowed the commit to be injected.
- toxik 6y ago
  As has been pointed out elsewhere, the exploit is the ability to inject code into the PHP Git repository. Not this RCE.