Some applications for Microsoft Windows may use unsafe methods for determining how to load DLLs. As a result, these applications can be forced to load a DLL from an attacker-controlled source rather than a trusted location.
Dynamically Linked Libraries (DLLs) are executable software components that are incorporated into a program at run-time rather than when the program is compiled and linked. Functions included in these libraries can be loaded in different ways by an application. In the case of run-time dynamic linking, a module uses the LoadLibrary()
or LoadLibraryEx()
functions to load the DLL at run time. If the location of the DLL to be loaded is not specified (such as specifying a fully qualified path name) by the application, Microsoft Windows defines an order in which directories are searched for the named DLL. By default, this search order contains the current directory of the process.
If an attacker can cause an affected application to call LoadLibrary()
while the application’s current directory is set to one controlled by the attacker, that application may run the attacker’s code from a specially named DLL also supplied in that directory. This can occur when the affected application opens a normal file typically associated with it from the attacker-controlled directory. The specific name of the DLL that an attacker would need to choose varies depending on the affected application.
A remote, unauthenticated attacker with the ability to supply a malicious DLL may be able to execute arbitrary code on a vulnerable system. In the most likely exploit scenario, an attacker could host this malicious DLL on a USB drive or network share. The attacker-supplied code would be run with the privileges of the user of the affected application.
In some cases of affected applications, an attacker who already has access to a local folder on the system could use this vulnerability in a local application running with elevated privileges to escalate their own privileges on the system.
Apply a patch from the vendor
The vulnerability described generically above can be manifest in a variety of software products. Please see the Vendor Information section of this document for information about specific applications that may be affected by this issue.
For Developers:
Ensure that applications do not load libraries from insecure locations
Developers of applications for the Windows platform should ensure that their applications call SetDllDirectory()
with a blank path before calling LoadLibrary()
to ensure that the DLL is not loaded from the current directory. More information about how to load libraries securely can be found in the following Microsoft articles: Dynamic-Link Library Security and Another technique for Fixing DLL Preloading attacks.
For Administrators:
Disable loading of libraries from the current working directory
According to Microsoft Security Advisory 2269637:
Note_ This workaround requires installation of the tool described in Microsoft Knowledge Base Article 2264107._
Microsoft has released a tool which allows customers to disable the loading of libraries from remote network or WebDAV shares. This tool can be configured to disallow insecure loading on a per-application or a global system basis.
Customers who are informed by their vendor of an application being vulnerable can use this tool to help protect against attempts to exploit this issue.
After the update listed in KB article 2264107 has been installed, the following registry value can be used to remove the current working directory from the default DLL search order:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager]
"CWDIllegalInDllSearch"=dword:ffffffff
Note that making this change may cause some applications to not behave properly.
Disable the WebClient service
According to Microsoft Security Advisory 2269637:
Disabling the WebClient service helps protect affected systems from attempts to exploit this vulnerability by blocking the most likely remote attack vector through the Web Distributed Authoring and Versioning (WebDAV) client service. After applying this workaround, it will still be possible for remote attackers who successfully exploited this vulnerability to cause Microsoft Office Outlook to run programs located on the targeted user’s computer or the Local Area Network (LAN), but users will be prompted for confirmation before opening arbitrary programs from the Internet.
To disable the WebClient Service, follow these steps:
While this workaround does not remove the vulnerability, it does block an attack vector for this vulnerability.
Block outgoing SMB traffic
This list is known to be incomplete.
707943
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Javascript is disabled. Click here to view vendors.
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
http://secunia.com/advisories/41198/
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: October 13, 2016
Statement Date: October 13, 2016
Affected
A DLL pre-loading issue existed in the Adobe Flash Player and Acrobat Reader DC installers for Windows. The problem has been fixed in the following versions:
- Installers for Adobe Flash Player
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41126/>
<http://secunia.com/advisories/41134/>
<http://secunia.com/advisories/41110/>
<http://secunia.com/advisories/41060/>
<http://secunia.com/advisories/41233/>
<http://secunia.com/advisories/41232/>
<http://secunia.com/advisories/41130/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: August 30, 2010
Statement Date: August 10, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41123/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41115/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 02, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41013/>
<http://secunia.com/advisories/41156/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: August 26, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41109/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 02, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41106/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: August 26, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41051/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41230/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: August 26, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41125/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: November 09, 2011
Affected
We have not received a statement from the vendor.
It has been reported that Mezzmo version 2.4.5.0 on Windows XP SP3 is vulnerable.
Updated: August 30, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41148/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Notified: August 30, 2010 Updated: August 30, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41142/>
<http://secunia.com/advisories/41174/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: August 30, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41146/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 27, 2010
Affected
Final Solution addressed by Bug Report BR10000097255. More technical information about the corresponding CATIA Bug Report are available for CATIA V5 customers on the DS Support site <http://www.3ds.com/support>.
We are not aware of further vendor information regarding this vulnerability.
Updated: August 30, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41108/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41227/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: January 25, 2011
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41228/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41226/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41231/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41225/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Notified: January 04, 2011 Updated: February 29, 2012
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
EnCase Law Enforcement/Government Edition version 7.03 is affected. Additional versions may also be affected.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41224/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41223/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: August 26, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41131/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41222/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41200/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41219/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 02, 2010
Statement Date: August 23, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41136/>
<http://secunia.com/advisories/41114/>
<http://secunia.com/advisories/41104/>
<http://secunia.com/advisories/41098/>
<http://secunia.com/advisories/41050/>
<http://secunia.com/advisories/41063/>
<http://secunia.com/advisories/41212/>
<http://secunia.com/advisories/41211/>
<http://secunia.com/advisories/41202/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 02, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41168/>
<http://secunia.com/advisories/41151/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41188/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41184/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: April 13, 2012
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Updated: August 26, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41093/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: July 13, 2016
Affected
“A DLL pre-loading issue existed in the Opera installer. This problem was addressed in Opera 37. Note that this was treated as an enhancement, not a security issue.”
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41083/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 02, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41135/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: August 26, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41103/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 02, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41176/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: August 26, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41092/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41178/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/product/14343/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: August 26, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41137/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41164/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: August 26, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41094/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: August 26, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41112/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: August 26, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41119/>
<http://secunia.com/advisories/41124/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41259/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 02, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41197/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: August 24, 2010
Statement Date: April 08, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Updated: August 26, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41107>
CVE-2010-3124
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 01, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41143/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 02, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41064/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
Updated: September 02, 2010
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
<http://secunia.com/advisories/41097/>
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23707943 Feedback>).
View all 54 vendors __View less vendors __
Group | Score | Vector |
---|---|---|
Base | 0 | AV:–/AC:–/Au:–/C:–/I:–/A:– |
Temporal | 0 | E:F/RL:TF/RC:ND |
Environmental | 0 | CDP:ND/TD:H/CR:ND/IR:ND/AR:ND |
Instances and variations of this vulnerability were independently discovered by a number of researchers, including Georgi Guninski; Simon Raner, Jure Skofic and Mitja Kolsek of ACROS Security; Taeho Kwon and Zhendong Su; H.D. Moore. Some vendor information comes from Secunia.
This document was written by Chad R Dougherty.
CVE IDs: | CVE-2010-1795 |
---|---|
Severity Metric: | 64.13 Date Public: |
blog.mandiant.com/archives/1207
blog.metasploit.com/2010/08/exploiting-dll-hijacking-flaws.html
blog.rapid7.com/?p=5325
blog.zoller.lu/2010/08/cve-2010-xn-loadlibrarygetprocaddress.html
blogs.msdn.com/b/david_leblanc/archive/2010/08/23/another-technique-for-fixing-dll-preloading-attacks.aspx
blogs.technet.com/b/srd/archive/2010/08/23/more-information-about-dll-preloading-remote-attack-vector.aspx
msdn.microsoft.com/en-us/library/Aa297182
msdn.microsoft.com/en-us/library/ms684175%28VS.85%29.aspx
support.microsoft.com/kb/2264107
www.acrossecurity.com/aspr/ASPR-2010-04-12-1-PUB.txt
www.acrossecurity.com/aspr/ASPR-2010-04-12-2-PUB.txt
www.acrossecurity.com/aspr/ASPR-2010-08-18-1-PUB.txt
www.cert.org/blogs/vuls/2008/09/carpet_bombing_and_directory_p.html
www.cs.ucdavis.edu/research/tech-reports/2010/CSE-2010-2.pdf
www.guninski.com/officedll.html
www.securityfocus.com/bid/1699/discuss
www.microsoft.com/technet/security/advisory/2269637.mspx