Skip to content

Auth0 angular-jwt misinterprets allowlist as regex

Moderate severity GitHub Reviewed Published May 14, 2022 to the GitHub Advisory Database • Updated Oct 19, 2023

Package

npm angular-jwt (npm)

Affected versions

< 0.1.10

Patched versions

0.1.10

Description

Auth0 angular-jwt before 0.1.10 treats whiteListedDomains entries as regular expressions, which allows remote attackers with knowledge of the jwtInterceptorProvider.whiteListedDomains setting to bypass the domain allowlist filter via a crafted domain.

For example, if the setting is initialized with:

jwtInterceptorProvider.whiteListedDomains = ['whitelisted.Example.com'];

An attacker can set up a domain whitelistedXexample.com that will pass the allow list filter, as it considers the . separator to be a regex whildcard which matches any character.

References

Published by the National Vulnerability Database Jun 19, 2018
Published to the GitHub Advisory Database May 14, 2022
Reviewed Oct 19, 2023
Last updated Oct 19, 2023

Severity

Moderate

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
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
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.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

EPSS score

0.139%
(51st percentile)

Weaknesses

CVE ID

CVE-2018-11537

GHSA ID

GHSA-vm2p-f5j4-mj6g

Source code

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