VIM GVim up to 7.3.09 User32.dll untrusted search path

Summaryinfo

A vulnerability has been found in VIM GVim and classified as critical. This impacts an unknown function in the library User32.dll. Performing a manipulation results in untrusted search path. This vulnerability is reported as CVE-2010-3914. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as very critical, was found in VIM GVim (Word Processing Software). This affects an unknown part in the library User32.dll. The manipulation with an unknown input leads to a untrusted search path vulnerability. CWE is classifying the issue as CWE-426. The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Untrusted search path vulnerability in VIM Development Group GVim before 7.3.034, and possibly other versions before 7.3.46, allows local users, and possibly remote attackers, to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse User32.dll or other DLL that is located in the same folder as a .TXT file. NOTE: some of these details are obtained from third party information.

The weakness was disclosed 11/03/2010 (Website). The advisory is shared at jvn.jp. This vulnerability is uniquely identified as CVE-2010-3914 since 10/12/2010. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/08/2019). MITRE ATT&CK project uses the attack technique T1574 for this issue.

Upgrading to version 7.3.028 eliminates this vulnerability.

The vulnerability is also documented in the databases at SecurityFocus (BID 44588†) and Secunia (SA42084†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Word Processing Software

Vendor

• VIM

Name

• GVim

Version

• 7.3.01
• 7.3.010
• 7.3.011
• 7.3.012
• 7.3.013
• 7.3.014
• 7.3.015
• 7.3.016
• 7.3.017
• 7.3.018
• 7.3.019
• 7.3.02
• 7.3.020
• 7.3.021
• 7.3.022
• 7.3.023
• 7.3.024
• 7.3.025
• 7.3.026
• 7.3.027
• 7.3.028
• 7.3.029
• 7.3.03
• 7.3.030
• 7.3.031
• 7.3.032
• 7.3.033
• 7.3.04
• 7.3.05
• 7.3.06
• 7.3.07
• 7.3.08
• 7.3.09

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion