Microsoft Security Bulletin MS12-061 - Important
Vulnerability in Visual Studio Team Foundation Server Could Allow Elevation of Privilege (2719584)
Published: September 11, 2012 | Updated: September 24, 2012
This security update resolves a privately reported vulnerability in Visual Studio Team Foundation Server. The vulnerability could allow elevation of privilege if a user clicks a specially crafted link in an email message or browses to a webpage that is used to exploit the vulnerability. In all cases, however, an attacker would have no way to force users to perform these actions. Instead, an attacker would have to convince users to visit a website, typically by getting them to click a link in an email message or Instant Messenger message that takes them to the attacker's website.
This security update is rated Important for all supported editions of Microsoft Visual Studio Team Foundation Server 2010. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerability by correcting how the Team Foundation Server site validates input parameters. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity.
Known Issues. Microsoft Knowledge Base Article 2719584 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues. When currently known issues and recommended solutions pertain only to specific releases of this software, this article provides links to further articles.
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, see Microsoft Support Lifecycle.
Microsoft Developer Tools and Software
|Software||Maximum Security Impact||Aggregate Severity Rating||Updates Replaced|
|Microsoft Visual Studio Team Foundation Server 2010 Service Pack 1
|Elevation of Privilege||Important||None|
Although no security updates are replaced by this update, this update is cumulative and replaces previous cumulative updates for Team Foundation Server 2010 Service Pack 1. See the related FAQ for more information.
|Microsoft Visual Studio .NET 2003 Service Pack 1|
|Microsoft Visual Studio 2005 Service Pack 1|
|Microsoft Visual Studio Team Foundation Server 2005 Service Pack 1|
|Microsoft Visual Studio 2008 Service Pack 1|
|Microsoft Visual Studio Team Foundation Server 2008 Service Pack 1|
|Microsoft Visual Studio 2010 Service Pack 1|
|Microsoft Visual Studio LightSwitch 2011|
|Microsoft Visual Studio 2012|
|Microsoft Visual Studio Team Foundation Server 2012|
Frequently Asked Questions (FAQ) Related to This Security Update
Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.
Where are the hashes of the security updates?
The SHA1 and SHA2 hashes of the security updates can be used to verify the authenticity of downloaded security update packages. For the hash information pertaining to this update, see Microsoft Knowledge Base Article 2719584.
Does this update contain any non-security related changes to functionality?
Yes. In addition to the changes that are listed in the Vulnerability Information section of this bulletin, this update includes other functionality changes as described in Microsoft Knowledge Base Article 2719584. Note that this update (KB2719584) is cumulative and replaces previous cumulative updates for Team Foundation Server 2010 Service Pack 1.
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, see the Microsoft Support Lifecycle website.
It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Service Pack Lifecycle Support Policy.
Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, see the Microsoft Worldwide Information website, select the country in the Contact Information list, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Microsoft Support Lifecycle Policy FAQ.
Severity Ratings and Vulnerability Identifiers
The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the September bulletin summary. For more information, see Microsoft Exploitability Index.
|Affected Software||XSS Vulnerability - CVE-2012-1892||Aggregate Severity Rating|
|Microsoft Visual Studio Team Foundation Server 2010 Service Pack 1||Important
Elevation of Privilege
XSS Vulnerability - CVE-2012-1892
A reflected XSS vulnerability exists in Visual Studio Team Foundation Server that could allow an attacker to inject a client-side script into the user's instance of Internet Explorer or any web browser using Team Foundation Server web access. The script could spoof content, disclose information, or take any action that the user could take on the site on behalf of the targeted user.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-1892.
Mitigating Factors for XSS Vulnerability - CVE-2012-1892
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
- In a web-based attack scenario, an attacker could host a website that contains a webpage that is used to exploit this vulnerability. In addition, compromised websites and websites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the attacker's website.
- The XSS Filter in Internet Explorer 8 and Internet Explorer 9 prevents this attack for Internet Explorer 8 and Internet Explorer 9 users when browsing to a website in the Internet Zone. The XSS Filter in Internet Explorer 8 and Internet Explorer 9 is not enabled by default in the Intranet Zone.
Workarounds for XSS Vulnerability - CVE-2012-1892
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
Enable Internet Explorer 8 and Internet Explorer 9 XSS filter in the Local intranet security zone
You can help protect against exploitation of this vulnerability by changing your settings to enable the XSS filter in the Local intranet security zone. (XSS filter is enabled by default in the Internet security zone.) To do this, perform the following steps:
- In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Local intranet, and then click Custom level.
- Under Settings, in the Scripting section, under Enable XSS filter, click Enable, and then click OK.
- Click OK two times to return to Internet Explorer.
Impact of workaround. Internal sites not previously flagged as being XSS risks could be flagged.
How to undo the workaround.
To undo this workaround, perform the following steps.
- In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Local intranet, and then click Custom level.
- Under Settings, in the Scripting section, under Enable XSS filter, click Disable, and then click OK.
- Click OK two times to return to Internet Explorer.
FAQ for XSS Vulnerability - CVE-2012-1892
What is the scope of the vulnerability?
This is a reflected XSS vulnerability that could lead to elevation of privilege.
What is cross-site scripting (XSS)?
Cross-site scripting (XSS) is a class of security vulnerability that can enable an attacker to inject script into the response to a webpage request. This script is then run by the requesting application, often times a web browser. The script could then spoof content, disclose information, or take any action that the user could take on the affected website, on behalf of the targeted user.
What causes the vulnerability?
The vulnerability is caused when Team Foundation Server improperly validates a request parameter on the Team Foundation Server site.
What is Visual Studio Team Foundation Server?
There are two sides to Team Foundation Server. On the one hand, it is a collection of features that are shared by the various members of a project team to enable them to work together more effectively. Team members can share project plans, work products, and progress assessments easily and naturally. On the other hand, Team Foundation Server is a platform specifically architected for integration and extensibility. Customers and partners can customize elements of Team Foundation Server and complement it with new functionality. Extensions can range from the very simple to the very complex. They can range from renaming a field in a work item, to integrating an entirely new tool. For more information about Team Foundations server, see Team Foundation Server Fundamentals: A Look at the Capabilities and Architecture.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could inject a client-side script into the user's instance of Internet Explorer. The script could spoof content, disclose information, or take any action that the user could take on the site on behalf of the targeted user.
How could an attacker exploit the vulnerability?
In an email attack scenario, an attacker could exploit the vulnerability by sending a specially crafted link to the user and convincing the user to click the link. In a web-based attack scenario, an attacker could convince the user to visit a webpage that contains specially crafted content designed to exploit the vulnerability.
What systems are primarily at risk from the vulnerability?
Servers running Visual Studio Team Foundation Server are primarily at risk from this vulnerability. Systems not running Visual Studio Team Foundation Server are not affected by this vulnerability and will not be offered the update.
What does the update do?
The update addresses the vulnerability by correcting how the Team Foundation Server site validates input parameters.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Detection and Deployment Tools and Guidance
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security website provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."
Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS12-001"), you can add all the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.
Detection and Deployment Guidance
Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) lets administrators scan local and remote systems for missing security updates as well as common security misconfigurations. For more information, see Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
|Microsoft Visual Studio Team Foundation Server 2010 Service Pack 1||Yes|
Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please see Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
Windows Server Update Services
Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
|Software||SMS 2003 with ITMU||System Center Configuration Manager|
|Microsoft Visual Studio Team Foundation Server 2010 Service Pack 1||Yes||Yes|
Note Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to System Center Configuration Manager. For customers remaining on SMS 2003 Service Pack 3, the Inventory Tool for Microsoft Updates (ITMU) is also an option.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager uses WSUS 3.0 for detection of updates. For more information, see System Center.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
For information about the specific security update for your affected software, click the appropriate link:
Microsoft Visual Studio Team Foundation Server 2010 (all editions)
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
|Inclusion in Future Service Packs||None|
|Installing without user intervention||For Microsoft Visual Studio Team Foundation Server 2010 Service Pack 1:
|Installing without restarting||For Microsoft Visual Studio Team Foundation Server 2010 Service Pack 1:
|Update log file||Not applicable|
|Further information||For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.|
|Restart required?||This update does not require a restart.|
|Removal Information||Use Add or Remove Programs item in Control Panel.|
|File Information||For Microsoft Visual Studio Team Foundation Server 2010 Service Pack 1:
See Microsoft Knowledge Base Article 2719584
|Registry Key Verification||Not applicable|
Installing the Update
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and Deployment Tools and Guidance subsection.
This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.
To install the 2.0 or later version of Windows Installer, visit one of the following Microsoft websites:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Microsoft Windows 2000
- Windows Installer 2.0 Redistributable for Microsoft Windows 2000 and Windows NT 4.0
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
|/? or /h or /help||Display usage dialog box.|
|/q[n|b|r|f]||Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI
|/quiet||Same as /q|
|/passive||Same as /qb|
|/extract [directory]||Extract the package to the specified directory.|
|/uninstall or /u||Uninstall this update.|
|/addsource or /as||Specifies the source path of the product msi. This option may be used when installing the update results in a prompt to insert the installation source media for the product. For example:
<update executable> /addsource "C:\Product MSI\Visual Studio\enu\vs_setup.msi" /addsource "C:\Product MSI\Net\Netfx.msi"
|/norestart||Do not restart after the installation is complete|
|/promptrestart||Prompts the user for restart if necessary|
|/forcerestart||Always restart the computer after installation|
|/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|] <LogFile>||i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
|/log <LogFile>||Equivalent of /l <LogFile>|
|/sendreport||Send installation data for this update to Microsoft as a Watson report. No personally identifiable information is sent.|
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
To remove this security update, use the Add or Remove Programs item in Control Panel.
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the “Microsoft baseline Security Analyzer” heading under the section, Microsoft Detection and Deployment Tools and Guidance.
File Version Verification
Note Because there are several versions and editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
- On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Microsoft thanks the following for working with us to help protect customers:
- Sunil Yadav of INR Labs (Network Intelligence India) for reporting the XSS Vulnerability (CVE-2012-1892)
Microsoft Active Protections Program (MAPP)
To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please go to the active protections websites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
How to obtain help and support for this security update
- Help installing updates: Support for Microsoft Update
- Security solutions for IT professionals: TechNet Security Troubleshooting and Support
- Help protect your computer that is running Windows from viruses and malware: Virus Solution and Security Center
- Local support according to your country: International Support
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
- V1.0 (August 14, 2012): Bulletin published.
- V1.1 (September 24, 2012): Modified the Recommendation section in the Executive Summary to reflect a change in the way the update is offered. This update is no longer offered automatically, but can be installed by checking online for updates from Microsoft Update. Customers who have already successfully updated their systems do not need to take any action. Also added a link to Microsoft Knowledge Base Article 2719584 under Known Issues in the Executive Summary.
Built at 2014-04-18T13:49:36Z-07:00