CVE-2016-7191: Authentication Bypass in passport-azure-ad
Summary
CVE-2016-7191: Authentication Bypass in passport-azure-ad. Affects passport-azure-ad across 2 version ranges.
>= 1.0.0, < 1.4.6
>= 2.0.0, < 2.0.1
Fixed in 1.4.6 or 2.0.1, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The passport-azure-ad package is an npm package used for authentication in Node.js applications with Azure Active Directory. It provides a strategy for authenticating users using Azure AD's OAuth 2.0 protocol. This package is widely used in applications that require Azure AD authentication.
Vulnerability Detail
The affected versions of passport-azure-ad do not recognize the validateIssuer setting, which allows remote attackers to bypass authentication by using a crafted token. This vulnerability can lead to unauthorized access to protected resources and potential data breaches. The severity of this vulnerability is rated as HIGH with a CVSS score of 8.1.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
>= 1.0.0, < 1.4.61.4.6npm install passport-azure-ad@1.4.6 -
>= 2.0.0, < 2.0.12.0.1npm install passport-azure-ad@2.0.1
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no known workaround for this vulnerability. It is crucial to update to the fixed versions mentioned above to mitigate the risk of authentication bypass.
Conclusion
In conclusion, the passport-azure-ad package is vulnerable to an authentication bypass issue that can lead to unauthorized access and data breaches. To mitigate this vulnerability, it is crucial to update to the fixed versions mentioned above. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for passport-azure-ad →
FAQ
This vulnerability allows remote attackers to bypass authentication, potentially leading to unauthorized access to protected resources and data breaches.
You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. It analyzes your package-lock.json file and provides real-time alerts for open-source vulnerabilities.
No, only versions prior to 1.4.6 for 1.x and versions prior to 2.0.1 for 2.x are affected. Updating to the fixed versions will resolve the vulnerability.
No, there is no known workaround. It is essential to update to the fixed versions to mitigate the risk.
The CVSS score for this vulnerability is 8.1, indicating a high severity.
