Skip to content

URL Redirection to Untrusted Site ('Open Redirect') in express-openid-connect

High severity GitHub Reviewed Published Mar 29, 2022 in auth0/express-openid-connect • Updated Jan 27, 2023

Package

npm express-openid-connect (npm)

Affected versions

< 2.7.2

Patched versions

2.7.2

Description

Impact

Users of the requiresAuth middleware, either directly or through the default authRequired option, are vulnerable to an Open Redirect when the middleware is applied to a catch all route.

If all routes under example.com are protected with the requiresAuth middleware, a visit to http://example.com//google.com will be redirected to google.com after login because the original url reported by the Express framework is not properly sanitised.

Am I affected?

You are affected by this vulnerability if you are using the requiresAuth middleware on a catch all route or the default authRequired option and express-openid-connect version <=2.7.1.

How to fix that?

Upgrade to version >=2.7.2

Will this update impact my users?

The fix provided in the patch will not affect your users.

References

@adamjmcgrath adamjmcgrath published to auth0/express-openid-connect Mar 29, 2022
Published to the GitHub Advisory Database Mar 31, 2022
Reviewed Mar 31, 2022
Published by the National Vulnerability Database Mar 31, 2022
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N

EPSS score

0.061%
(27th percentile)

Weaknesses

CVE ID

CVE-2022-24794

GHSA ID

GHSA-7p99-3798-f85c

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.