3 ms·
I think the underlying cause was the same - unescaped output that was supplied by the (malicious) user.
by Getahobby 16y ago
I think the underlying cause was the same - unescaped output that was supplied by the (malicious) user.
- nbpoole 16y agoMmm, from here it looks like YouTube had a sanitizer in place that failed: it's not clear that the Android Market was sanitizing the output here. That's what I meant by the underlying cause being different.