Microsoft Azure DevOps Server and Team Foundation Server Cross Site Scripting Vulnerability

Description

Microsoft Team Foundation Server is prone to a cross-site scripting vulnerability because it fails to properly sanitize user-supplied input. An attacker may leverage this issue to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This can allow the attacker to steal cookie-based authentication credentials and launch other attacks. Note: This issue was previously titled ‘Microsoft Team Foundation Server CVE-2019-0871 Cross Site Scripting Vulnerability’. The title have been changed to better reflect the underlying products affected.

Technologies Affected

• Microsoft Azure DevOps Server 2019
• Microsoft Team Foundation Server 2017 Update 3.1
• Microsoft Team Foundation Server 2018 Update 1.2
• Microsoft Team Foundation Server 2018 Update 3.2

Recommendations

Run all software as a nonprivileged user with minimal access rights.
Attackers may successfully exploit client flaws in the browser through cross-site scripting vulnerabilities. When possible, run client software as regular user accounts with limited access to system resources. This may limit the immediate consequences of client-side vulnerabilities.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to detect and block attacks and anomalous activity such as requests containing suspicious URI sequences. Since the webserver may log such requests, review its logs regularly.

Do not follow links provided by unknown or untrusted sources.
Web users should be cautious about following links to websites that are provided by unfamiliar or suspicious sources. Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.

Set web browser security to disable the execution of script code or active content.
Since exploiting cross-site scripting issues often requires malicious script code to run in browsers, consider disabling script code and active content support within a client browser as a way to prevent a successful exploit. Note that this mitigation tactic might adversely affect legitimate sites that rely on the execution of browser-based script code.

Updates are available. Please see the references or vendor advisory for more information.