An attacker who successfully exploits this vulnerability could bypass Azure Active Directory authentication to a targeted host web application. To exploit this vulnerability, an attacker would have to send a specially crafted token to the target web application that contains a valid user's identity claims. This update addresses the vulnerability by correcting how ID tokens are validated when Passport strategies take advantage of Azure Active Directory.
Frequently asked questions about this vulnerabilityQ1: I use Azure Active Directory. Am I affected?
A1: This vulnerability only affects web applications that use the Passport-Azure-AD for Node.js library to take advantage of Azure AD for authentication. Standard Azure AD authentication that does not use the Passport-Azure-AD for Node.js library is not affected. The vulnerability exists in web applications that use outdated versions of the Passport-Azure-AD for Node.js library.
Q2: What is Passport-Azure-AD for Node.js?
A2: Passport-Azure-AD for Node.js is a collection of Passport strategies that help you integrate your node applications with Azure Active Directory. It includes OpenID Connect, WS-Federation, and SAML-P authentication and authorization. These providers let you use the many features of Passport-Azure-AD for Node.js, including web single sign-on (WebSSO), Endpoint Protection with OAuth, and JWT token issuance and validation.
Update informationDevelopers who use the Passport Azure AD Node.js library must download the latest version of the Passport-Azure-AD for Node.js library, and then update their applications. The technical details are published in our GitHub repository.
Developers who use version 1.x must update to version 1.4.6.
Developers who use version 2.0 must update to version 2.0.1.
Article ID: 3187742 - Last Review: Oct 1, 2016 - Revision: 1