Lucene search

K
securityvulnsSecurityvulnsSECURITYVULNS:DOC:24579
HistoryAug 26, 2010 - 12:00 a.m.

Security update available for Shockwave Player

2010-08-2600:00:00
vulners.com
18

Security update available for Shockwave Player

Release date: August 24, 2010

Vulnerability identifier: APSB10-20

CVE number:CVE-2010-2863, CVE-2010-2864, CVE-2010-2865, CVE-2010-2866,
CVE-2010-2867, CVE-2010-2868, CVE-2010-2869, CVE-2010-2870, CVE-2010-2871, CVE-2010-2872, CVE-2010-2873, CVE-2010-2874, CVE-2010-2875, CVE-2010-2876, CVE-2010-2877, CVE-2010-2878, CVE-2010-2879, CVE-2010-2880, CVE-2010-2881, CVE-2010-2882

Platform: Windows and Macintosh
Summary

Critical vulnerabilities have been identified in Adobe Shockwave Player 11.5.7.609 and earlier versions on the Windows and Macintosh operating systems. The vulnerabilities could allow an attacker, who successfully exploits these vulnerabilities, to run malicious code on the affected system. Adobe recommends users of Adobe Shockwave Player 11.5.7.609 and earlier versions update to Adobe Shockwave Player 11.5.8.612, using the instructions provided below.
Affected software versions

Shockwave Player 11.5.7.609 and earlier versions for Windows and Macintosh
Solution

Adobe recommends users of Adobe Shockwave Player 11.5.7.609 and earlier versions upgrade to the newest version 11.5.8.612, available here: http://get.adobe.com/shockwave/.
Severity rating

Adobe categorizes this as a critical update and recommends that users apply the update for their product installations.
Details

Critical vulnerabilities have been identified in Adobe Shockwave Player 11.5.7.609 and earlier versions on the Windows and Macintosh operating systems. The vulnerabilities could allow an attacker, who successfully exploits these vulnerabilities, to run malicious code on the affected system. Adobe recommends users of Adobe Shockwave Player 11.5.7.609 and earlier versions update to Adobe Shockwave Player 11.5.8.612, using the instructions provided above.

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2863).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2864).

This update resolves a denial of service issue (CVE-2010-2865).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2866).

This update resolves a pointer offset vulnerability that could lead to code execution (CVE-2010-2867).

This update resolves multiple denial of service issues; arbitrary code execution has not been demonstrated, but may be possible (CVE-2010-2868).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2869).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2870).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2871).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2872).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2873).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2874).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2875).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2876).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2877).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2878).

This update resolves an integer overflow vulnerability that could lead to code execution (CVE-2010-2879).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2880).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2881).

This update resolves a memory corruption vulnerability that could lead to code execution (CVE-2010-2882).
Acknowledgments

Adobe would like to thank the following individuals and organizations for reporting the relevant issues and for working with Adobe to help protect our customers:

* Honggang Ren of Fortinet's FortiGuard Labs (CVE-2010-2863, CVE-2010-2864, CVE-2010-2865)
* TippingPoint FuzzBox as driven by Aaron Portnoy and Logan Brown (CVE-2010-2866, CVE-2010-2867, CVE-2010-2870)
* Rodrigo Rubira Branco of Check Point (CVE-2010-2864, CVE-2010-2868, CVE-2010-2869, CVE-2010-2880, CVE-2010-2881, CVE-2010-2882)
* An Anonymous Researcher through TippingPoint's Zero Day Initiative (CVE-2010-2871)
* Damian Put through TippingPoint's Zero Day Initiative (CVE-2010-2872, CVE-2010-2873)
* An Anonymous Researcher through TippingPoint's Zero Day Initiative (CVE-2010-2874)
* An Anonymous Researcher reported through iDefense's Vulnerability Contributor Program (CVE-2010-2875)
* An Anonymous Researcher through TippingPoint's Zero Day Initiative (CVE-2010-2876)
* Aaron Portnoy, Logan Brown, and Team lollersk8erz (CVE-2010-2874, CVE-2010-2877, CVE-2010-2878)
* Aaron Portnoy, Logan Brown, and Team Montreal Hotties (CVE-2010-2879)