Fascinating read overall. I've used 3 of the ones you mentioned - none of these CVEs allowing code execution are open now - they are all many years old (3-4)
be serious.
your current PDF reader has unpatched zero day remote exploits, most certainly based on simple logic and statistics and past. Most work for many years before being discovered. And grey and white hats no longer even give a crap about pdf considering it something useless to favor now that the world should be using epub or rtf
CVE lists are no longer updated in recent years, and researchers no longer do as much free testing of compromised machines.
experts also want newbsto use built in pdf coming to browsers that is slow but 100% (yes 100%) written in javacript :
but it is so buggy it crashes doing font width tests this week in all apple products, and the main devs refuse to alter their crashing code and want apple to alter 15 years of prior installed products. (seriously)
try 0 points 3.7 years ago
be serious.
your current PDF reader has unpatched zero day remote exploits, most certainly based on simple logic and statistics and past. Most work for many years before being discovered. And grey and white hats no longer even give a crap about pdf considering it something useless to favor now that the world should be using epub or rtf
CVE lists are no longer updated in recent years, and researchers no longer do as much free testing of compromised machines.
experts also want newbsto use built in pdf coming to browsers that is slow but 100% (yes 100%) written in javacript :
https://github.com/mozilla/pdf.js/
but it is so buggy it crashes doing font width tests this week in all apple products, and the main devs refuse to alter their crashing code and want apple to alter 15 years of prior installed products. (seriously)
Linux retardation causes forks. I predict death or a fork of https://github.com/mozilla/pdf.js/
tl/dr : your pdf reader is compromised