50 CVEs in 50 Days: Fuzzing Adobe Reader
As much as many of us lament the state of much of today&#x27;s software, if you think of products from a certain era - IE6, Flash, Java web applets - they all had a commonality in their code quality. These are mostly a non-issue these days, but it&#x27;s not because they suddenly stopped having bugs and still get active use.<p>I remember rolling out Adobe Reader in those days and as a product, I don&#x27;t believe its core has changed much. They&#x27;ve certainly managed to bolt on a whole lot of new features, but that can only make the position worse.<p>As much as this sounds like a call to kill Adobe, something needs to happen before that&#x27;s feasible. For the average enterprise, Adobe Reader is far more ingrained than these products were. Case in point, in organisation I asked the question of whether Chrome&#x27;s PDF viewer would cut it for them. One large department then ordered Adobe Professional for every user. They told me they didn&#x27;t need it, they just knew I wouldn&#x27;t propose removing a product they&#x27;d actually paid for.<p>Adobe Reader needs its HTML5 moment - an alternative that&#x27;s not just &quot;good enough for most people&quot;, but one that&#x27;s actually better.