3 ms·
They weren't getting the latter, they specifically went in there looking to mitigate what a theoretical content injection attack could do. > In a relatively un
by scrollaway 10y ago
They weren't getting the latter, they specifically went in there looking to mitigate what a theoretical content injection attack could do.
> In a relatively unique project, we asked Cure53 to assess what an attacker could do, assuming a content injection bug in GitHub.com