Multiple Security Vulnerabilities in Adobe Reader for Solaris 10 May Allow Execution of Arbitrary Code or Cause Denial of Service (DoS) - Adobe Security Bulletin APSB09-15 |
|
| Category : | Security |
| Release Phase : | Resolved |
| Bug Id : | 6891381
|
| Product : | Solaris 10 Operating System
|
| Date of Workaround Release : | 22-Oct-2009
|
| Date of Resolved Release : | 30-Nov-2009
|
Multiple Security Vulnerabilities in Adobe Reader for Solaris 10 May Allow Execution of Arbitrary Code or Cause Denial of Service (DoS) - Adobe Security Bulletin APSB09-15
1. Impact
Multiple security vulnerabilities in Adobe Reader versions 9.x before
9.1.4, 8.x before 8.1.7 and 7.x before 7.1.4 may allow remote
unprivileged users to execute arbitrary code or crash the Adobe Reader
application, thereby causing a Denial of Service (DoS) condition. These
vulnerabilities may be exploited via specially crafted PDF files.
The following resources document these issues in more detail:
2. Contributing Factors
These issues can occur in the
following release:
SPARC Platform
Notes:
1. Solaris 8, Solaris 9, Solaris 10 on the x86 platform and OpenSolaris
do not ship Adobe Reader and therefore are not affected by these issues.
2. All versions of Adobe Reader 9 prior to 9.2, Adobe Reader 8 prior to
8.1.7 and Adobe Reader 7 prior to 7.1.4 are affected by these issues.
To determine the version of Adobe Reader installed on the system, the
following command can be run:
$ /usr/bin/acroread -version
7.0.1
Earlier versions of Adobe Reader on Solaris 10 only shipped acroread in
/usr/sfw/bin which do not support the '-version' option, so for such
instances, the following command can be used instead:
$ cat `pkgchk -l -P AcroVersion | awk '/Pathname/ { print $2 }'`
5.0.10
3. Symptoms
There are no predictable symptoms that would indicate these issues have
been exploited to execute arbitrary code.
If the described issues have been exploited to cause a Denial of
Service (DoS), the Adobe Reader application will crash, potentially
leaving a core(4) file depending on the system configuration.
4. Workaround
To avoid the described issues, do not load PDF files from untrusted
sources.
Until patches can be applied, the risk of some of these vulnerabilities
can be mitigated by preventing PDF documents from being opened
automatically by the Web browser. In Firefox 2.0, this can be set by
changing the default action for PDF documents with the following:
1. Open the Preferences dialog from the
Edit menu
2. Select Contents tab.
3. Click on Manage button in File Types block.
4. Select PDF in the list and click Change Action.
5. Select 'Save them on my computer' option and click OK.
Note that this workaround will reduce the risk of exploitation but will
not prevent the issues from being exploited.
5. Resolution
SPARC Platform
For more information on
Security Sun Alerts, see Technical
Instruction
ID 213557.
This Sun Alert
notification is being provided to you on
an "AS IS"
basis. This Sun Alert notification may contain information provided by
third parties. The issues described in this Sun Alert notification may
or may not impact your system(s). Sun makes no representations,
warranties, or guarantees as to the information contained herein. ANY
AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU
ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT
OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This
Sun Alert notification contains Sun proprietary and confidential
information. It is being provided to you pursuant to the provisions of
your agreement to purchase services from Sun, or, if you do not have
such an agreement, the Sun.com Terms of Use. This Sun Alert
notification may only be used for the purposes contemplated by these
agreements.
Copyright 2000-2009 Sun
Microsystems,
Inc., 4150 Network Circle, Santa
Clara, CA 95054 U.S.A. All rights reservedModification History26-Oct-2009: Updated Impact for CVE Reference CVE-2009-2579
30-Nov-2009: Updated Contributing Factors and Resolution sections; now Resolved
AttachmentsThis solution has no attachment