News for hackers. Stuff that matters.
[dead]
Re:Countering threats from North Korea by Thorrez on Sunday March 27, 2022 @05:01PM (#30824103)
Because of the various safeguards:

> Only serving the iframe at specific times, presumably when they knew an intended target would be visiting the site.

> In some email campaigns the targets received links with unique IDs. This was potentially used to enforce a one-time-click policy for each link and allow the exploit kit to only be served once.

> The exploit kit would AES encrypt each stage, including the clients’ responses with a session-specific key.

> Additional stages were not served if the previous stage failed.

it was hard to collect the exploits. They only managed to collect the Chrome one.

Compare this to Pegasus, malware that attacks both iOS and Android. So far researchers have only been able to collect iOS versions.

I think it's a little funny that you're complaining that a Google security group (TAG in this case) is publicly reporting vulnerabilities in a Google product, but not others. With Project Zero (a different Google security group), people usually complain in the opposite way, and say that it's bad for Google to publicly report a lot of vulnerabilities in competitor products, because it makes competitors look bad and is just done for publicity reasons.

Disclosure, I work at Google, but not on anything related to this.

Re:Countering threats from North Korea by huntsman on Sunday March 27, 2022 @05:50PM (#30824506)
In this case we only obtained a Chrome exploit.

Whether that means they didn’t have exploits for other platforms as part of this attack or that we just didn’t succeed in determining them is unknown.

TAG has certainly found and reported exploits in other platforms many times so it is not a matter of not caring.

Source: I am lead of TAG at Google

Re:Countering threats from North Korea by yunohn on Sunday March 27, 2022 @04:09PM (#30823610)
I think you misunderstood - they’re saying the links served nothing, presumably because it’s a Chrome-specific exploit.
Re:Countering threats from North Korea by joshuamorton on Sunday March 27, 2022 @04:15PM (#30823665)
Or potentially there were exploits but they weren't able to encounter them due to the various protection measures the attackers used.
Re:Countering threats from North Korea by yunohn on Sunday March 27, 2022 @04:55PM (#30824038)
Either way, I find it very hard to believe that they haven’t coordinated with Apple and Mozilla on this CVE.
Re:Countering threats from North Korea by joshuamorton on Sunday March 27, 2022 @08:16PM (#30825556)
There's nothing to coordinate with on this cve. There's almost assuredly coordination happening between the various security orgs, but this cve is about a chrome bug, and the Google teams weren't able to isolate ff or safari zero days to report.

"We expect this group has zero days that they're exploiting in your software but we don't know what specifically they are" isn't a cve.

Re:Countering threats from North Korea by SheinhardtWigCo on Sunday March 27, 2022 @04:35PM (#30823842)
"We did not recover" is ambiguous.