Advisory Published
Updated

CVE-2021-41580

First published: Mon Sep 27 2021(Updated: )

** DISPUTED ** The passport-oauth2 package before 1.6.1 for Node.js mishandles the error condition of failure to obtain an access token. This is exploitable in certain use cases where an OAuth identity provider uses an HTTP 200 status code for authentication-failure error reports, and an application grants authorization upon simply receiving the access token (i.e., does not try to use the token). NOTE: the passport-oauth2 vendor does not consider this a passport-oauth2 vulnerability.

Credit: cve@mitre.org cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Passportjs Passport-oauth2<1.6.1
IBM Cloud Pak for Business Automation<=V23.0.1 - V23.0.1-IF002
IBM Cloud Pak for Business Automation<=V21.0.3 - V21.0.3-IF024
IBM Cloud Pak for Business Automation<=V22.0.2 - V22.0.2-IF006 and later fixesV22.0.1 - V22.0.1-IF006 and later fixesV21.0.2 - V21.0.2-IF012 and later fixesV21.0.1 - V21.0.1-IF007 and later fixesV20.0.1 - V20.0.3 and later fixesV19.0.1 - V19.0.3 and later fixesV18.0.0 - V18.0.2 and later fixes
<1.6.1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the vulnerability ID for this issue?

    The vulnerability ID for this issue is CVE-2021-41580.

  • What is the severity of CVE-2021-41580?

    The severity of CVE-2021-41580 is medium with a CVSS score of 5.3.

  • How does CVE-2021-41580 impact Node.js passport-oauth2 module?

    CVE-2021-41580 can allow a remote attacker to obtain sensitive information by exploiting a mishandling of error condition in the Node.js passport-oauth2 module.

  • What is the affected software for CVE-2021-41580?

    The affected software is IBM Cloud Pak for Business Automation, versions V23.0.1-IF002, V21.0.3-IF024, V22.0.2-IF006 and later fixes, V21.0.1-IF007 and later fixes, V20.0.1-V20.0.3 and later fixes, V19.0.1-V19.0.3 and later fixes, V18.0.0-V18.0.2 and later fixes.

  • How can an attacker exploit CVE-2021-41580?

    An attacker can exploit CVE-2021-41580 by sending a specially-crafted request to obtain access token information and potentially launch further attacks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203