ID CVE-2018-1037
Summary An information disclosure vulnerability exists when Visual Studio improperly discloses limited contents of uninitialized memory while compiling program database (PDB) files, aka "Microsoft Visual Studio Information Disclosure Vulnerability." This affects Microsoft Visual Studio.
References
Vulnerable Configurations
  • Microsoft Visual Studio 2010 Service Pack 1
    cpe:2.3:a:microsoft:visual_studio:2010:sp1
  • cpe:2.3:a:microsoft:visual_studio:2012:update5
    cpe:2.3:a:microsoft:visual_studio:2012:update5
  • cpe:2.3:a:microsoft:visual_studio:2013:update5
    cpe:2.3:a:microsoft:visual_studio:2013:update5
  • cpe:2.3:a:microsoft:visual_studio:2015:update3
    cpe:2.3:a:microsoft:visual_studio:2015:update3
  • cpe:2.3:a:microsoft:visual_studio:2017
    cpe:2.3:a:microsoft:visual_studio:2017
  • cpe:2.3:a:microsoft:visual_studio:2017:15.6.6
    cpe:2.3:a:microsoft:visual_studio:2017:15.6.6
  • cpe:2.3:a:microsoft:visual_studio:2017:15.7:preview
    cpe:2.3:a:microsoft:visual_studio:2017:15.7:preview
CVSS
Base: 4.3
Impact:
Exploitability:
CWE CWE-200
CAPEC
  • Subverting Environment Variable Values
    The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
  • Footprinting
    An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Browser Fingerprinting
    An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Reusing Session IDs (aka Session Replay)
    This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
  • Using Slashes in Alternate Encoding
    This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
msbulletin via4
bulletin_SOURCE_FILE https://portal.msrc.microsoft.com/api/security-guidance/en-us/
cves_url https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-1037
impact Information Disclosure
knowledgebase_SOURCE_FILE
knowledgebase_id
name Microsoft Visual Studio 2017 Version 15.6.6
publishedDate 2018-04-10T07:00:00
severity Important
nessus via4
NASL family Windows
NASL id SMB_NT_MS18_APR_VISUAL_STUDIO.NASL
description The Microsoft Visual Studio Products are missing a security update. It is, therefore, affected by the following vulnerability : - An information disclosure vulnerability exists when Visual Studio improperly discloses limited contents of uninitialized memory while compiling program database (PDB) files. An attacker who took advantage of this information disclosure could view uninitialized memory from the Visual Studio instance used to compile the PDB file. To take advantage of the vulnerability, an attacker would require access to an affected PDB file created using a vulnerable version of Visual Studio. An attacker would have no way to force a developer to produce this information disclosure. The security update addresses the vulnerability by correcting how PDB files are generated when a project is compiled. (CVE-2018-1037)
last seen 2018-08-18
modified 2018-08-17
plugin id 109029
published 2018-04-13
reporter Tenable
source https://www.tenable.com/plugins/index.php?view=single&id=109029
title Security Updates for Microsoft Visual Studio Products (April 2018)
refmap via4
bid 103715
confirm https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-1037
sectrack 1040664
Last major update 11-04-2018 - 21:29
Published 11-04-2018 - 21:29
Last modified 17-05-2018 - 10:55
Back to Top