CIS CYBER SECURITY ADVISORIES
MS-ISAC CYBER SECURITY ADVISORY NUMBER:
Multiple Vulnerabilities in Adobe Shockwave Player Could Allow For Remote Code Execution (APSB11-19) - RISK: HIGH
- Shockwave Player 22.214.171.1246 and earlier versions for Windows and Macintosh
- Large and medium government entities: High
- Small government entities: High
- Large and medium business entities: High
- Small business entities: High
Home users: High
Adobe Shockwave Player is prone to multiple memory corruption vulnerabilities that could allow for remote code execution. Details of these vulnerabilities are as follows:
- A memory corruption vulnerability exists in the 'IML32.dll' library component that could lead to remote code execution.
- A memory corruption vulnerability occurs when Shockwave Player parses a '.dir' media file in the 'Dirapi.dll' library component that could lead to remote code execution.
- A memory corruption vulnerability exists in the 'Textra.x32' component that could lead to remote code execution.
- A memory corruption vulnerability exists in the 'msvcr90.dll' library component that could lead to remote code execution.
- Multiple unspecified memory corruption vulnerabilities could lead to remote code execution.
These vulnerabilities may be exploited if a user visits or is redirected to a specially crafted web page or when a user opens a specially crafted file. Successful exploitation could result in an attacker gaining the same privileges as the logged on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Failed exploit attempts will likely crash the affected application.
We recommend the following actions be taken:
- Install the 126.96.36.1999 update from Adobe immediately after appropriate testing.
- Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack.
- Do not open email attachments or follow web links from unknown or untrusted sources.
- Consider implementing file extension white lists for allowed e-mail attachments.