Adobe Critical Security Updates For: Acrobat, Reader and Flash plus ColdFusion

--

Another second-Tuesday-of-the-month, another bunch of Adobe critical security updates.

I) Adobe Acrobat and Adobe Reader

Security Updates available for Adobe Reader and Acrobat

Details

Adobe has released security updates for Adobe Reader and Acrobat for Windows and Macintosh. These updates address vulnerabilities that could potentially allow an attacker to take over the affected system.  Adobe recommends users update their product installations to the latest versions:

Users of Adobe Reader XI (11.0.09) and earlier versions should update to version 11.0.10.
Users of Adobe Reader X (10.1.12) and earlier versions should update to version 10.1.13.
Users of Adobe Acrobat XI (11.0.09) and earlier versions should update to version 11.0.10.
Users of Adobe Acrobat X (10.1.12) and earlier versions should update to version 10.1.13. 

These updates resolve use-after-free vulnerabilities that could lead to code execution (CVE-2014-8454, CVE-2014-8455, CVE-2014-9165).

These updates resolve heap-based buffer overflow vulnerabilities that could lead to code execution (CVE-2014-8457, CVE-2014-8460, CVE-2014-9159).

These updates resolve an integer overflow vulnerability that could lead to code execution (CVE-2014-8449).

These updates resolve memory corruption vulnerabilities that could lead to code execution (CVE-2014-8445, CVE-2014-8446, CVE-2014-8447, CVE-2014-8456, CVE-2014-8458, CVE-2014-8459, CVE-2014-8461, CVE-2014-9158).

These updates resolve a time-of-check time-of-use (TOCTOU) race condition that could be exploited to allow arbitrary write access to the file system (CVE-2014-9150).

These updates resolve an improper implementation of a Javascript API that could lead to information disclosure (CVE-2014-8448, CVE-2014-8451).

These updates resolve a vulnerability in the handling of XML external entities that could lead to information disclosure (CVE-2014-8452).

These updates resolve vulnerabilities that could be exploited to circumvent the same-origin policy (CVE-2014-8453).  

Update Adobe Acrobat HERE:
http://www.adobe.com/support/downloads/product.jsp?product=1&platform=Macintosh

Update Reader HERE:
https://get.adobe.com/reader/

II) Adobe Flash Player

Security updates available for Adobe Flash Player

Details

Adobe has released security updates for Adobe Flash Player for Windows, Macintosh and Linux.  These updates address vulnerabilities that could potentially allow an attacker to take control of the affected system. Adobe recommends users update their product installations to the latest versions:

Users of the Adobe Flash Player desktop runtime for Windows and Macintosh should update to Adobe Flash Player 16.0.0.235.
Users of the Adobe Flash Player Extended Support Release should update to Adobe Flash Player 13.0.0.259.
Users of Adobe Flash Player for Linux should update to Adobe Flash Player 11.2.202.425.
Adobe Flash Player installed with Google Chrome, as well as Internet Explorer on Windows 8.x, will automatically update to the current version.

These updates resolve memory corruption vulnerabilities that could lead to code execution (CVE-2014-0587, CVE-2014-9164).

These updates resolve a use-after-free vulnerability that could lead to code execution (CVE-2014-8443).

These updates resolve a stack-based buffer overflow vulnerability that could lead to code execution (CVE-2014-9163).

These updates resolve an information disclosure vulnerability (CVE-2014-9162).

These updates resolve a vulnerability that could be exploited to circumvent the same-origin policy (CVE-2014-0580). 

Download Flash Player HERE:
https://get.adobe.com/flashplayer/

III) ColdFusion

Security Update: Hotfixes available for ColdFusion

Details

Adobe has released security hotfixes for ColdFusion versions 11 and 10.  These hotfixes address a resource consumption issue that could potentially result in a denial of service (CVE-2014-9166).

Update instructions and further details are HERE:

ColdFusion 10 Update 15

ColdFusion 11 Update 3

--

The Safari Security Update That Wasn't: Whatever Happened to 8.0.1, 7.1.1 and 6.2.1???

~~
[UPDATE 2014-12-11: Apple has now released Safari 8.0.2, 7.1.2 and 6.2.2. I'll be writing them up as soon as their security document is posted online. In the meantime, I'm going to guess that the ~mysterious~ security document for 8.0.1, 7.1.1 and 6.2.1 applies.]
~~

It's a 

~mystery~

Dateline: December 3rd, 2014 at 5:01 pm EST. 

I received a notice by email that Apple had released security updates of Safari, versions 8.0.1, 7.1.1 and 6.2.1. Because I was using OS X 10.10.1 Yosemite at the time, I managed to get Safari 8.0.1 installed and running just before it suddenly...

~vanished~

...off the Internet. Gone too were 7.1.1 and 6.2.1. The trio have never been seen again!

And yet on December 4th, 2014, the security announcement I had received by email ~mysteriously~ appeared on the Internet and has remained there ever since as an ominous spectre reminding the reader of what was, but is not, but may someday be.

Brave readers can glimpse this ~mysterious~ document themselves, before it too...

~vanishes~

http://support.apple.com/en-us/HT6596

Don't bother searching the net for the three updates. They aren't there. They aren't anywhere! ...Except on one of my Yosemite volumes. I played with 8.0.1 for about an hour and sensed nothing wrong. I had no idea that I was playing with something DEAD. Never once did I intuit that I was surfing the net with something that didn't exist, not in life as we know it. Now I'm unsure if I should run 8.0.1 again. I'm scared!

If the authorities rediscover these updates in the corporeal world, I'll be examining them closely in order to determine if their security patches are the same as those that ~vanished~ or if they are instead 
doppelgängers!

~~

[BTW: I have to comment, isn't it soooo Apple to have a security update released, then wait days for its security document to be released on the net.... While here we have a security update release that Apple pulled, and yet its security document remains on the net?! Why can't Apple coordinate its security updates AND its security documents? Is that so hard? Is it Apple???]

~~