Microsoft SharePoint CVE-2013-3179 Multiple HTML Injection Vulnerabilities

Description

Microsoft SharePoint is prone to multiple HTML-injection vulnerabilities because it fails to properly sanitize user-supplied input. Attacker-supplied HTML and script code could be executed in the context of the affected site, potentially allowing the attacker to steal cookie-based authentication credentials or control how the site is rendered to the user; other attacks are also possible.

Technologies Affected

• Microsoft SharePoint Foundation 2010 SP1
• Microsoft SharePoint Foundation 2010 SP2
• Microsoft SharePoint Foundation 2013
• Microsoft SharePoint Server 2007 for 32-bit SP3
• Microsoft SharePoint Server 2007 for 64-bit SP3
• Microsoft SharePoint Server 2010 SP1
• Microsoft SharePoint Server 2010 SP2
• Microsoft SharePoint Server 2013
• Microsoft Windows SharePoint Services for 32-bit 3.0 SP3
• Microsoft Windows SharePoint Services for 64-bit 3.0 SP3

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.