Adobe, not wanting to be accused of being careless, like the Microsoft crowd, has decided to release an explanation for the lack of jumping on a repair for the problem plaguing the ever-attacked Acrobat Reader. (Some may call it Adobe Reader, but I happen to have a memory, and know what it was called from the start.)

ComputerWorld gives the reasoning –

Adobe chose to wait until mid-January to patch a critical PDF bug because issuing an emergency update would have disrupted its quarterly security update schedule, the company said today.

Unless users apply one of the workarounds that Adobe’s suggested, the decision will leave systems open to attack until Jan. 12, when the patch is released. According to several security firms, the flaw has been in use by criminals since at least Nov. 20. Adobe only found out Monday that the vulnerability in its Reader and Acrobat applications was being actively exploited.

“We had two options,” said Brad Arkin, Adobe’s director for product security and privacy, describing the company’s conundrum. “We could do an out-of-cycle update for this one vulnerability, and get out something as fast as we could, or try to work it into the Jan. 12 release.”

The former, which would have gotten a fix for the current zero-day to users within “two or three weeks,” said Arkin, had a down side. By pulling engineers into the Reader/Acrobat patch job, Adobe would have had to push back the already-scheduled Jan. 12 update into at least February.

“There really wasn’t a third option,” Arkin claimed, explaining that it would have been impossible for Adobe to do both — rush an emergency patch to people by the end of December, then turn around and still meet the Jan. 12 deadline for updates already in progress.

“With a lot of work over the holidays, we decided we could get the patch into the code base for the Jan. 12 release, and still make that,” Arkin said.

Helping to make Adobe’s decision, Arkin argued, was the workaround it urged on users in a security advisory published late Monday. “We think we have an effective mitigation, the JavaScript Blacklist, which we included with the October security update.”

JavaScript Blacklist Framework is a new feature that Adobe added to Reader and Acrobat that lets users and enterprise administrators lock down specific JavaScript functions, or APIs (application programming interfaces) to protect machines against known attacks without disabling all JavaScript functionality.

“This is the first time that we’re using JavaScript Blacklist as a mitigation,” said Arkin. Internal tests confirmed that by switching off the vulnerable API, users would be safe from the in-the-wild exploits making the rounds.

Though it might be easy to dismiss the Adobe attitude as one of disinterest, we must remember that the code is written by people, and they have holidays, and time off, as well as we do.

Hoping for a complete and bug-free program come January is probably the course we should take. With a little extra time, it might be longer before the next exploit.


72 Virgins

soon to be a new series on TNT! Starring Betty White as Sister Mary Elephant!

Opera, the fastest and most secure web browser