Any application running on the Microsoft Windows platform that uses dynamically linked libraries (DLLs) may be affected. Whether or not an application is vulnerable depends on how it specifically loads a DLL. Please see the Vendor Information section of Vulnerability Note VU#707943 for information about specific vendors.
Due to the way Microsoft Windows loads dynamically linked libraries (DLLs), an application may load an attacker-supplied DLL instead of the legitimate one, resulting in the execution of arbitrary code.
Microsoft Windows supports dynamically linked libraries (DLLs) that are loaded when needed by an application. DLLs are typically loaded when the application is first started; however DLLs may be loaded and unloaded while the application is running. An application can request a DLL file in a variety of ways, and Windows uses several different search algorithms to find DLL files. The interaction between the application and Windows can result in a DLL file being loaded from the current working directory of the application, instead of the Windows system directory or the directory where the application is installed.
The current working directory could be the desktop, a removable storage device such as a USB key, a Windows file share, or a WebDAV location. When a file associated with an application is opened, a DLL in the same directory as the file may be loaded. Although an attacker may not have permission to write to the Windows system or application directories, the attacker may be able to write a DLL to a directory used to store files, or the attacker could provide their own directory.
Attacks against this type of vulnerability have been referred to as "binary planting." Please see Vulnerability Note VU#707943 and Microsoft Security Advisory 2269637 for more information.
By placing a DLL with the correct name (and possibly the relative directory path) in the current working directory, an attacker could execute arbitrary code with the privileges of the application that loads the DLL.
Individual applications that run on the Windows platform may require patches or updates. Microsoft Knowledge Base article KB2264107 describes an update that provides a registry key that can prevent Windows from searching the current working directory for DLL files.
Information about specific solutions for different vendors, general mitigation techniques, and secure ways for applications to load DLLs can be found in the Vendor Information and Solution sections of Vulnerability Note VU#707943.
Feedback can be directed to US-CERT.
Produced 2010 by US-CERT, a government organization. Terms of use
August 26, 2010: Initial release
Adobe has released Security Bulletin APSB10-17, which describes multiple vulnerabilities affecting Adobe Reader and Acrobat.
Adobe Security Bulletin APSB10-17 describes a number of vulnerabilities affecting Adobe Reader and Acrobat. These vulnerabilities affect Reader and Acrobat 9.3.3, earlier 9.x versions, 8.2.3, and earlier 8.x versions.
An attacker could exploit these vulnerabilities by convincing a user to open a specially crafted PDF file. The Adobe Reader browser plug-in, which can automatically open PDF documents hosted on a website, is available for multiple web browsers and operating systems.
These vulnerabilities could allow a remote attacker to execute arbitrary code, write arbitrary files or folders to the file system, escalate local privileges, or cause a denial of service on an affected system as the result of a user opening a malicious PDF file.
Update
Adobe has released updates to address this issue. Users are encouraged to read Adobe Security Bulletin APSB10-17 and update vulnerable versions of Adobe Reader and Acrobat.
Disable JavaScript in Adobe Reader and Acrobat
Disabling JavaScript may prevent some exploits from resulting in code execution. Acrobat JavaScript can be disabled using the Preferences menu (Edit -> Preferences -> JavaScript; uncheck Enable Acrobat JavaScript).
Adobe provides a framework to blacklist specific
JavaScipt APIs. If JavaScript must be enabled, this feature may be useful
when specific APIs are known to be vulnerable or used in attacks.
Prevent Internet Explorer from automatically opening PDF files
The installer for Adobe Reader and Acrobat configures Internet Explorer to
automatically open PDF files without any user interaction. This behavior can be
reverted to a safer option that prompts the user by importing the following as a
.REG file:
Windows Registry Editor Version
5.00
[HKEY_CLASSES_ROOT\AcroExch.Document.7]
"EditFlags"=hex:00,00,00,00
Disable the display of PDF
files in the web browser
Preventing PDF files from opening
inside a web browser will partially mitigate this vulnerability. If this
workaround is applied, it may also mitigate future vulnerabilities.
To prevent PDF files from automatically being opened in a web browser, do the
following:
1. Open Adobe Acrobat Reader.
2. Open the
Edit menu.
3. Choose the Preferences option.
4.
Choose the Internet section.
5. Uncheck the "Display PDF
in browser" checkbox.
Do not access PDF files from
untrusted sources
Do not open unfamiliar or unexpected PDF
files, particularly those hosted on websites or delivered as email attachments.
Please see Cyber Security Tip ST04-010.
Feedback can be directed to US-CERT.
Produced 2010 by US-CERT, a government organization. Terms of use
August 19, 2010: Initial release
Other Adobe products that support Flash may also be vulnerable.
According to Adobe Security Bulletin APSB10-16, there are vulnerabilities in Adobe Flash and AIR. These vulnerabilities affect Flash Player, AIR, and possibly other products that support Flash. A remote attacker could exploit these vulnerabilities to execute arbitrary code.
Adobe Security Bulletin APSB10-16 describes vulnerabilities in Adobe Flash that affect Flash Player and AIR. These vulnerabilities may also affect other products that independently support Flash, such as Adobe Reader, Acrobat, Photoshop, Photoshop Lightroom, Freehand MX, and Fireworks.
An attacker could exploit these vulnerabilities by convincing a user to open specially crafted Flash content. Flash content is commonly hosted on a web page, but it can also be embedded in a PDF and other documents or provided as a stand-alone file.
If a user opens specially crafted Flash content, a remote attacker may be able to execute arbitrary code.
Update Flash and AIR
Adobe Security Bulletin APSB10-16 recommends updating to Flash Player 10.1.82.76 or 9.0.280 and to AIR 2.0.3. This will update the Flash web browser plug-in and ActiveX control, as well as AIR. However, it will not update Flash support in Adobe Reader, Acrobat, or other products.
To reduce your exposure to these and other Flash vulnerabilities, consider the following mitigation technique.
Disable Flash in your web browser
Uninstall Flash or restrict which sites are allowed to run Flash. To the extent possible, only run trusted Flash content on trusted domains. For more information, see Securing Your Web Browser.
Additional workarounds are available in US-CERT Vulnerability Note VU#660993.
Feedback can be directed to US-CERT.
Produced 2010 by US-CERT, a government organization. Terms of use
August 11, 2010: Initial release
Microsoft has released updates to address vulnerabilities in Microsoft Windows, Microsoft Office, Internet Explorer, Microsoft .NET Framework, and Microsoft Silverlight.
The Microsoft Security Bulletin Summary for August 2010 describes multiple vulnerabilities in Microsoft Windows, Microsoft Office, Internet Explorer, Microsoft .NET framework, and Microsoft Silverlight. Microsoft has released updates to address the vulnerabilities.
One of the bulletins released, MS10-046, addresses a previously identified vulnerability in the Windows Shell that is actively being exploited. This vulnerability was also described in US-CERT Vulnerability Note VU#940193.
A remote, unauthenticated attacker could execute arbitrary code or cause a vulnerable system or application to crash.
Apply updates
Microsoft has provided updates
for these vulnerabilities in the Microsoft
Security Bulletin Summary for August 2010. The security bulletin describes
any known issues related to the updates. Administrators are encouraged to note
these issues and test for any potentially adverse effects. Administrators should
consider using an automated update distribution system such as Windows
Server Update Services (WSUS).
Feedback can be directed to US-CERT.
Produced 2010 by US-CERT, a government organization. Terms of use
August 10, 2010: Initial release
The Oracle products and components listed above are affected by multiple vulnerabilities. The impacts of these vulnerabilities include remote execution of arbitrary code, information disclosure, and denial of service.
The Oracle Critical Patch Update Advisory - July 2010 addresses 59 vulnerabilities in various Oracle products and components, including 21 vulnerabilities in Sun products. The Advisory provides information about affected components, access and authorization required for successful exploitation, and the impact from the vulnerabilities on data confidentiality, integrity, and availability.
Oracle has associated CVE identifiers with the vulnerabilities addressed in this Critical Patch Update. If significant additional details about vulnerabilities and remediation techniques become available, we will update the Vulnerability Notes Database.
The impact of these vulnerabilities varies depending on the product, component, and configuration of the system. Potential consequences include the execution of arbitrary code or commands, information disclosure, and denial of service. Vulnerable components may be available to unauthenticated, remote attackers. An attacker who compromises an Oracle database may be able to access sensitive information.
Apply the appropriate patches or upgrade as specified in the Oracle Critical Patch Update Advisory - July 2010. Note that this document only lists newly corrected issues. Updates to patches for previously known issues are not listed.
Feedback can be directed to US-CERT.
Produced 2010 by US-CERT, a government organization. Terms of use
July 13, 2010: Initial release
Microsoft has released updates to address vulnerabilities in Microsoft Windows and Microsoft Office.
The Microsoft Security Bulletin Summary for July 2010 describes multiple vulnerabilities in Microsoft Windows and Microsoft Office. Microsoft has released updates to address the vulnerabilities.
One of the bulletins released, MS10-042, addresses a previously identified vulnerability in the Windows Help and Support Center that is actively being exploited. This vulnerability was also described in US-CERT Vulnerability Note VU#578319.
A remote, unauthenticated attacker could execute arbitrary code or cause a vulnerable system or application to crash.
Apply updates
Microsoft has provided updates
for these vulnerabilities in the Microsoft
Security Bulletin Summary for July 2010. The security bulletin describes any
known issues related to the updates. Administrators are encouraged to note these
issues and test for any potentially adverse effects. Administrators should
consider using an automated update distribution system such as Windows
Server Update Services (WSUS).
Feedback can be directed to US-CERT.
Produced 2010 by US-CERT, a government organization. Terms of use
July 13, 2010: Initial release
Other Adobe products that support Flash may also be vulnerable.
According to Adobe Security Bulletin APSB10-14, there are vulnerabilities in Adobe Flash and AIR. These vulnerabilities affect Flash Player, AIR, and possibly other products that support Flash. A remote attacker could exploit these vulnerabilities to execute arbitrary code.
Adobe Security Bulletin APSB10-14 describes vulnerabilities in Adobe Flash that affects Flash Player and AIR. It may also affect other products that independently support Flash, such as Adobe Reader, Acrobat, Photoshop, Photoshop Lightroom, Freehand MX, and Fireworks.
An attacker could exploit these vulnerabilities by convincing a user to open specially crafted Flash content. Flash content is commonly hosted on a web page, but it can also be embedded in a PDF and other documents or provided as a stand-alone file.
One of these vulnerabilities, CVE-2010-1297, is being exploited against Flash Player, Adobe Reader, and Acrobat. Additional information about CVE-2010-1297 is available in US-CERT Technical Cyber Security Alert TA10-159A and US-CERT Vulnerability Note VU#486225.
If a user opens specially crafted Flash content, a remote attacker may be able to execute arbitrary code.
Update Flash and AIR
Adobe Security Bulletin APSB10-14 recommends updating to Flash Player 10.1.53.64 or 9.0.277.0 and AIR to 2.0.2.12610. This will update the Flash web browser plug-in and ActiveX control and AIR, but will not update Flash support in Adobe Reader, Acrobat, or other products.
To reduce your exposure to these and other Flash vulnerabilities, consider the following mitigation technique.
Disable Flash in your web browser
Uninstall Flash or restrict which sites are allowed to run Flash. To the extent possible, only run trusted Flash content on trusted domains. For more information, see Securing Your Web Browser.
Feedback can be directed to US-CERT.
Produced 2010 by US-CERT, a government organization. Terms of use
June 11, 2010: Initial release
Microsoft has released updates to address vulnerabilities in Microsoft Windows, Microsoft Internet Explorer, Microsoft Office, Microsoft SharePoint Services, and Microsoft .NET Framework.
The Microsoft Security Bulletin Summary for June 2010 describes vulnerabilities in Microsoft Windows, Internet Explorer, Office, SharePoint Services, and .NET Framework. Microsoft has released updates to address the vulnerabilities.
A remote, unauthenticated attacker could execute arbitrary code or cause a vulnerable application to crash.
Apply updates
Microsoft has provided updates
for these vulnerabilities in the Microsoft
Security Bulletin Summary for June 2010. The security bulletin describes any
known issues related to the updates. Administrators are encouraged to note these
issues and test for any potentially adverse effects. Administrators should
consider using an automated update distribution system such as Windows
Server Update Services (WSUS).
Feedback can be directed to US-CERT.
Produced 2010 by US-CERT, a government organization. Terms of use
June 08, 2010: Initial release
Other Adobe products that support Flash may also be vulnerable.
According to Adobe, there is a vulnerability in Adobe Flash. This vulnerability affects Flash Player, Reader, Acrobat, and possibly other products that support Flash. A remote attacker could exploit this vulnerability to execute arbitrary code.
Adobe Security Advisory APSA10-01 describes a vulnerability in Adobe Flash that affects Flash Player, Reader, and Acrobat. It may also affect other products that independently support Flash, such as Photoshop, Photoshop Lightroom, Freehand MX, and Fireworks.
An attacker could exploit this vulnerability by convincing a user to open specially crafted Flash content. Flash content is commonly hosted on a web page, but it can also be embedded in PDF and other documents or provided as a stand-alone file.
As noted in APSA10-01, "There are reports that this vulnerability is being actively exploited in the wild against both Adobe Flash Player, and Adobe Reader and Acrobat."
Additional information is available in US-CERT Vulnerability Note VU#486225.
If a user opens specially crafted Flash content, a remote attacker may be able to execute arbitrary code.
Update
Adobe Security Advisory APSA10-01 suggests updating to the release candidate of Flash Player 10.1.
Disable Flash in your web browser
Uninstall Flash or restrict which sites are allowed to run Flash. To the extent possible, only run trusted Flash content on trusted domains. For more information, see Securing Your Web Browser.
Disable Flash in Adobe Reader and Acrobat
Disabling Flash in Adobe Reader will mitigate attacks that rely on Flash content embedded in a PDF file. Disabling 3D & Multimedia support does not directly address the vulnerability, but it does provide additional mitigation and results in a more user-friendly error message instead of a crash. To disable Flash and 3D & Multimedia support in Adobe Reader 9, delete, rename, or remove access to these files:
Microsoft Windows
"%ProgramFiles%\Adobe\Reader
9.0\Reader\authplay.dll"
"%ProgramFiles%\Adobe\Reader
9.0\Reader\rt3d.dll"
Apple Mac OS
X
"/Applications/Adobe Reader 9/Adobe
Reader.app/Contents/Frameworks/AuthPlayLib.bundle"
"/Applications/Adobe Reader 9/Adobe
Reader.app/Contents/Frameworks/Adobe3D.framework"
GNU/Linux (locations may vary among distributions)
"/opt/Adobe/Reader9/Reader/intellinux/lib/libauthplay.so"
"/opt/Adobe/Reader9/Reader/intellinux/lib/librt3d.so"
File locations may be different for Adobe Acrobat or other Adobe products that include Flash and 3D & Multimedia support. Disabling these plugins will reduce functionality and will not protect against SWF files hosted on websites. Depending on the update schedule for products other than Flash Player, consider leaving Flash and 3D & Multimedia support disabled unless they are absolutely required.
Prevent Internet Explorer from automatically opening PDF documents
The installer for Adobe Reader and Acrobat configures Internet Explorer to automatically open PDF files without any user interaction. This behavior can be reverted to a safer option that prompts the user by importing the following as a .REG file:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\AcroExch.Document.7]
"EditFlags"=hex:00,00,00,00
Disable the display of PDF documents in the web browser
Preventing PDF documents from opening inside a web browser will partially mitigate this vulnerability. If this workaround is applied, it may also mitigate future vulnerabilities.
To prevent PDF documents from automatically being opened in a web browser, do the following:
Disable JavaScript in Adobe Reader and Acrobat
Disabling JavaScript provides some additional protection against attacks. Acrobat JavaScript can be disabled using the Preferences menu (Edit -> Preferences -> JavaScript; uncheck Enable Acrobat JavaScript).
Enable DEP in Microsoft Windows
Consider enabling Data Execution Prevention (DEP) in supported versions of Windows. DEP should not be treated as a complete workaround, but it can mitigate the execution of attacker-supplied code in some cases. Microsoft has published detailed technical information about DEP in Security Research & Defense blog posts "Understanding DEP as a mitigation technology" part 1 and part 2. Use of DEP should be considered in conjunction with the application of patches or other mitigations described in this document.
Do not access
PDF documents from untrusted sources
Do not open unfamiliar or
unexpected PDF documents, particularly those hosted on websites or delivered as
email attachments. Please see Cyber Security Tip ST04-010.
Feedback can be directed to US-CERT.
Produced 2010 by US-CERT, a government organization. Terms of use
June 08, 2010: Initial release
Microsoft has released updates to address vulnerabilities in Microsoft Outlook Express, Microsoft Windows Mail, Microsoft Windows Live Mail, Microsoft Office, and Microsoft Visual Basic for Applications.
Microsoft has released security bulletins for multiple vulnerabilities in Microsoft Outlook Express, Microsoft Windows Mail, Microsoft Windows Live Mail, Microsoft Office, and Microsoft Visual Basic for Applications. These bulletins are described in the Microsoft Security Bulletin Summary for May 2010.
Third-party software that distributes VBE6.DLL may also be affected. If the third-party application follows the best practices for using a shared component as a side-by-side assembly, then the component will be updated by the update provided by MS10-031. Otherwise, you should contact the vendor to obtain an updated version of the application with the fixed VBE6.DLL file.
A remote, unauthenticated attacker could execute arbitrary code or cause a vulnerable application to crash.
Apply updates from Microsoft
Microsoft has
provided updates for these vulnerabilities in the Microsoft
Security Bulletin Summary for May 2010. The security bulletin describes any
known issues related to the updates. Administrators are encouraged to note these
issues and test for any potentially adverse effects. Administrators should
consider using an automated update distribution system such as Windows
Server Update Services (WSUS).
Feedback can be directed to US-CERT.
Produced 2010 by US-CERT, a government organization. Terms of use
May 11, 2010: Initial release