SharonKoch / Wiki_Demo

Wiki.js | A modern and powerful wiki app built on Node.js
https://js.wiki
GNU Affero General Public License v3.0
1 stars 0 forks source link

passport-google-oauth20-2.0.0.tgz: 1 vulnerabilities (highest severity is: 5.3) - autoclosed #106

Closed mend-for-github-com[bot] closed 3 months ago

mend-for-github-com[bot] commented 4 months ago
Vulnerable Library - passport-google-oauth20-2.0.0.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/passport-google-oauth20/node_modules/passport-oauth2/package.json,/node_modules/passport-discord/node_modules/passport-oauth2/package.json,/node_modules/passport-twitch-strategy/node_modules/passport-oauth2/package.json,/node_modules/passport-github2/node_modules/passport-oauth2/package.json,/node_modules/passport-gitlab2/node_modules/passport-oauth2/package.json,/node_modules/@exlinc/keycloak-passport/node_modules/passport-oauth2/package.json,/node_modules/passport-facebook/node_modules/passport-oauth2/package.json,/node_modules/passport-oauth/node_modules/passport-oauth2/package.json,/node_modules/passport-slack-oauth2/node_modules/passport-oauth2/package.json

Found in HEAD commit: b544ab1bdcd701c07884add83f9af162c4523c4e

Vulnerabilities

CVE Severity CVSS Dependency Type Fixed in (passport-google-oauth20 version) Remediation Possible**
CVE-2021-41580 Medium 5.3 passport-oauth2-1.5.0.tgz Transitive N/A*

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2021-41580 ### Vulnerable Library - passport-oauth2-1.5.0.tgz

OAuth 2.0 authentication strategy for Passport.

Library home page: https://registry.npmjs.org/passport-oauth2/-/passport-oauth2-1.5.0.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/passport-google-oauth20/node_modules/passport-oauth2/package.json,/node_modules/passport-discord/node_modules/passport-oauth2/package.json,/node_modules/passport-twitch-strategy/node_modules/passport-oauth2/package.json,/node_modules/passport-github2/node_modules/passport-oauth2/package.json,/node_modules/passport-gitlab2/node_modules/passport-oauth2/package.json,/node_modules/@exlinc/keycloak-passport/node_modules/passport-oauth2/package.json,/node_modules/passport-facebook/node_modules/passport-oauth2/package.json,/node_modules/passport-oauth/node_modules/passport-oauth2/package.json,/node_modules/passport-slack-oauth2/node_modules/passport-oauth2/package.json

Dependency Hierarchy: - passport-google-oauth20-2.0.0.tgz (Root Library) - :x: **passport-oauth2-1.5.0.tgz** (Vulnerable Library)

Found in HEAD commit: b544ab1bdcd701c07884add83f9af162c4523c4e

Found in base branch: main

### Vulnerability Details

** 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.

Publish Date: 2021-09-27

URL: CVE-2021-41580

### CVSS 3 Score Details (5.3)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: None

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41580

Release Date: 2021-09-27

Fix Resolution: passport-oauth2 - 1.6.1

mend-for-github-com[bot] commented 3 months ago

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.