3 ms·
Looking at the timeline from http://www.protekresearchlab.com/index.php?option=com_content&view=article&id=40&Itemid=40 http://www.protekresearchlab.com/index.p
by JoachimSchipper 14y ago
Looking at the timeline from http://www.protekresearchlab.com/index.php?option=com_content&view=article&id=40&Itemid=40 http://www.protekresearchlab.com/index.php?option=com_conten...,
2011-09-20 Vulnerability reported to Adobe
2012-03-20 Publication of this advisory
(180 days after reporting to the vendor)
Adobe may have been blindsided, thinking that they'd "get around to fixing that one of those years".
That said, there is even a proof of concept available (see bottom of linked page), so this is rather serious.
- rsynnott 14y agoWell, Adobe had to wait til they had the new version out for people to upgrade to.
- exDM69 14y agoOr they could have pushed a minor security upgrade that fixes this bug. For free. It's probably a simple buffer overflow bug and can be fixed with a change to only a few lines of code. After the problem has been identified, it takes roughly 10 minutes of coding to fix the issue and perhaps a day or two for regular testing and distribution processes.