ID CVE-2008-3294
Summary src/configure.in in Vim 5.0 through 7.1, when used for a build with Python support, does not ensure that the Makefile-conf temporary file has the intended ownership and permissions, which allows local users to execute arbitrary code by modifying this file during a time window, or by creating it ahead of time with permissions that prevent its modification by configure.
References
Vulnerable Configurations
  • cpe:2.3:a:vim:vim:5.0:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:5.1:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:5.2:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:5.3:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:5.4:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:5.5:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:5.5:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:5.6:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:5.6:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:5.7:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:5.7:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:5.8:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:5.8:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:6.0:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:6.1:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:6.2:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:6.3:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:6.4:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:6.4:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:7.0:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:vim:vim:7.1:*:*:*:*:*:*:*
    cpe:2.3:a:vim:vim:7.1:*:*:*:*:*:*:*
CVSS
Base: 3.7 (as of 11-10-2018 - 20:47)
Impact:
Exploitability:
CWE CWE-94
CAPEC
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Manipulating User-Controlled Variables
    This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An attacker can override environment variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the attacker can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.
Access
VectorComplexityAuthentication
LOCAL HIGH NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
cvss-vector via4 AV:L/AC:H/Au:N/C:P/I:P/A:P
refmap via4
apple APPLE-SA-2008-10-09
bid 31681
bugtraq
  • 20080717 Vim: Insecure Temporary File Creation During Build: Arbitrary Code Execution
  • 20080718 Re: Vim: Insecure Temporary File Creation During Build: Arbitrary Code Execution
  • 20080725 Re: [Full-disclosure] Vim: Insecure Temporary File Creation During Build: Arbitrary Code Execution
confirm http://support.apple.com/kb/HT3216
fulldisc 20080717 Vim: Insecure Temporary File Creation During Build: Arbitrary Code Execution
secunia
  • 31159
  • 32222
vupen
  • ADV-2008-2146
  • ADV-2008-2780
statements via4
contributor Tomas Hoger
lastmodified 2008-07-25
organization Red Hat
statement This issue can only be exploited during the package build and it does not affect users of pre-built packages distributed with Red Hat Enterprise Linux. Therefore, we do not plan to backport a fix for this issue to already released version of Red Hat Enterprise Linux 2.1, 3, 4, and 5.
Last major update 11-10-2018 - 20:47
Published 24-07-2008 - 18:41
Back to Top