3rd-party “micropatch” for a vulnerability in Acrobat Reader

We have just published our own "micropatch" for a remotely exploitable memory corruption vulnerability in Adobe's Acrobat Reader DC, which was fixed by Adobe with their latest update.

Why did we do this? We want to fix the way vulnerabilities are getting fixed (the sheer amount of breaches tells us something is broken here), and we're going to do it with micropatching.

Vulnerability micropatching is a refreshing alternative to traditional security updates, which replace a large chunk of a software application or operating system, often require a restart and are tremendously difficult to revert in case of any problems. Our mighty little patching machine, 0patch (pronounced 'zero patch', https://0patch.com), allows for creation and deployment of tiny patches that can be applied directly and instantaneously to the memory of a running process, and can also be removed just as easily. No restarts either way.

For more information, please see our blog post "Writing a 0patch for Acrobat Reader's Use-After-Free Vulnerability CVE-2016-1077" (http://0patch.blogspot.com/2016/06/writing-0patch-for-acrobat-readers-use.h tml).

0patch team https://0patch.com @0patch