4 ms·
It's hard to beat a static PNG via the browser, rendered from Far Far Away, on Google's servers... https://docs.google.com/viewer?embedded=true&url=https://www
by vy8vWJlco 14y ago
It's hard to beat a static PNG via the browser, rendered from Far Far Away, on Google's servers...
https://docs.google.com/viewer?embedded=true&url=https://www.securelist.com/en/downloads/vlpdfs/themysteryofthepdf0-dayassemblermicrobackdoor.pdf https://docs.google.com/viewer?embedded=true&url=https:/...
Given the volume of PDFs Google must render, I wonder if they have had any security issues from the service.
- Scaevolus 14y agoIt's very hard to write an exploit when executable, environment, and countermeasures are all unknown.
- kordless 14y agoYeah, because the image viewers are always secure, right? http://technet.microsoft.com/en-us/security/bulletin/MS09-062 http://technet.microsoft.com/en-us/security/bulletin/MS09-06...
- apendleton 14y agoAs far as this discussion is concerned, yes. Exploiting a vulnerability that requires specially-crafted images isn't practical if the images are being generated by Google. You would need to find a vulnerability in Google's PDF renderer that let you cause it to generate an image that contained an additional exploit mechanism that would take advantage of the GDI bug. Sounds highly improbable.