ID CVE-2015-1769
Summary Mount Manager in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT Gold and 8.1, and Windows 10 mishandles symlinks, which allows physically proximate attackers to execute arbitrary code by connecting a crafted USB device, aka "Mount Manager Elevation of Privilege Vulnerability."
Vulnerable Configurations
  • Microsoft Windows 10 64-bit
  • Microsoft Windows 10 32-bit
  • cpe:2.3:o:microsoft:windows_7:-:sp1:-:-:-:-:x64
  • cpe:2.3:o:microsoft:windows_7:-:sp1:-:-:-:-:x86
  • cpe:2.3:o:microsoft:windows_8:-:-:-:-:-:-:x64
  • cpe:2.3:o:microsoft:windows_8:-:-:-:-:-:-:x86
  • Microsoft Windows 8.1 x64 (64-bit)
  • Microsoft Windows 8.1 x86 (32-bit)
  • Microsoft Windows RT
  • Microsoft Windows RT Gold
  • Microsoft Windows RT 8.1
  • Microsoft Windows Server 2008 Service Pack 2
  • Microsoft Windows Server 2008 R2 Service Pack 1
  • Microsoft Windows Server 2012 Gold
  • Microsoft Windows Server 2012 R2 DataCenter Edition
  • Microsoft Windows Server 2012 R2 Essentials Edition
  • Microsoft Windows Server 2012 R2 Standard Edition
  • Microsoft Windows Vista Service Pack 2
Base: 7.2 (as of 16-10-2015 - 10:07)
  • Symlink Attack
    An attacker positions a symbolic link in such a manner that the targeted user or application accesses the link's endpoint, assuming that it is accessing a file with the link's name. The endpoint file may be either output or input. If the file is output, the result is that the endpoint is modified, instead of a file at the intended location. Modifications to the endpoint file may include appending, overwriting, corrupting, changing permissions, or other modifications. In some variants of this attack the attacker may be able to control the change to a file while in other cases they cannot. The former is especially damaging since the attacker may be able to grant themselves increased privileges or insert false information, but the latter can also be damaging as it can expose sensitive information or corrupt or destroy vital system or application files. Alternatively, the endpoint file may serve as input to the targeted application. This can be used to feed malformed input into the target or to cause the target to process different information, possibly allowing the attacker to control the actions of the target or to cause the target to expose information to the attacker. Moreover, the actions taken on the endpoint file are undertaken with the permissions of the targeted user or application, which may exceed the permissions that the attacker would normally have.
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • 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://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 Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
msbulletin via4
bulletin_id MS15-085
date 2015-08-11T00:00:00
impact Elevation of Privilege
knowledgebase_id 3082487
severity Important
title Vulnerability in Mount Manager Could Allow Elevation of Privilege
nessus via4
NASL family Windows : Microsoft Bulletins
description The remote Windows host is affected by an elevation of privilege vulnerability in the Mount Manager component due to improper processing of symbolic links. A local attacker can exploit this vulnerability by inserting a malicious USB device into a user's system, allowing the writing of a malicious binary to disk and the execution of arbitrary code.
last seen 2019-02-21
modified 2018-11-15
plugin id 85330
published 2015-08-11
reporter Tenable
title MS15-085: Vulnerability in Mount Manager Could Allow Elevation of Privilege (3082487)
refmap via4
ms MS15-085
sectrack 1033244
Last major update 16-10-2015 - 14:05
Published 14-08-2015 - 20:59
Last modified 12-10-2018 - 18:09
Back to Top