Symptoms 1: Outlook Web App Token Spoofing Vulnerability
A token spoofing vulnerability exists in Microsoft Exchange Server. It could allow an attacker to send email messages that seem to come from a trusted source, and the messages contain a link to a website of the attacker. In a web-based attack scenario, an attacker could host a website that is used to try exploiting this vulnerability. Additionally, compromised websites and websites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. However, in almost every case, an attacker cannot force users to view the attacker controlled content. Instead, an attacker would have to convince users to take action, typically by having them click a link in an email message or Instant Messenger message, to take users to his or her website.
Symptoms 2: Exchange URL Redirection Vulnerability
An attacker can redirect a user to an arbitrary URL from a link that seems to originate from a known or trusted domain.
To generate the malicious link, an attacker must already be an authenticated Exchange user and be able to send email messages.
The malicious link could be sent in an email, but the attacker would have to convince users to open the link in order to exploit the vulnerability.
Symptoms 3: Multiple Outlook Web App XSS Vulnerabilities
An attacker who successfully exploits these vulnerabilities could read content that he or she is not authorized to read. The attacker could also use the identity of the victim to take actions on the Outlook Web App site on behalf of the victim, such as changing permissions, deleting content, and injecting malicious content in the browser of the victim.
Cause for Symptoms 1
This issue occurs because Outlook Web App does not properly validate a request token.
Cause for Symptoms 2
This issue occurs because Outlook Web App does not properly validate redirection tokens.
Cause for Symptoms 3
This issue occurs because Exchange Server does not properly validate input.
Method 1: Windows Update
This update is available from Windows Update.
Method 2: Microsoft Update Catalog
To get the stand-alone package for this update, go to the Microsoft Update Catalog website.
Method 3: Install an update
We recommend installing Cumulative Update 7 or a later update that contains this security fix for Exchange Server 2013.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.