Exploiting a bug in a memory unsafe language is much harder than writing some JavaScript. It is also much less reliable and platform specific.
The real question is why the hell is Firefox not sandboxed?
Not for long if this keeps up…
Did you know Acrobat supports viewing 3D models in PDFs? Not even kidding[1]. It has an unnecessarily huge attack surface.
I will never use that and I work in engineering at a factory.
[1] For example, http://help.actify.com/download/attachments/6651965/SF_expor...
Can you clarify what you mean by this?
But, I'm doubtful there would have been all that many CVEs issued for Acrobat from 1993-1998. There was only one CVE that mentioned "Acrobat" each year from 1999-2001, and three in 2002. The more recent years are the fun ones - but I have no idea whether that's a result of freshly-introduced exploitable bugs or just increased attention.
[0]: https://en.wikipedia.org/wiki/Adobe_Acrobat_version_history
http://www.sumatrapdfreader.org/free-pdf-reader.html
Not perfect but definitely not adobe or foxit and way safer than viewing in any browser.
Browsers are at least sandboxed and have heavily scrutinised codebases.
A quick Google search found only four:
https://www.mozilla.org/en-US/security/advisories/mfsa2013-9... (another local file disclosure)
https://www.mozilla.org/en-US/security/advisories/mfsa2015-3... (needs to be "combined with a separate vulnerability" to be exploitable)
https://www.mozilla.org/en-US/security/advisories/mfsa2015-6... (needs to be "combined with a separate vulnerability" to be exploitable)
https://www.mozilla.org/en-US/security/advisories/mfsa2015-7... (this one)
It still is looking better than the plugin it replaced.