PT-2018-10645 · Angular · Angular-Jwt

Stephan Hauser · Published 2018-06-19 · Updated 2022-05-14 · CVE-2018-11537

Positive Technologies (AI Summary)

CVSS v3.1

6.5

Medium

Base vector

AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Name of the Vulnerable Software and Affected Versions angular-jwt versions prior to 0.1.10

Description The issue allows remote attackers with knowledge of the jwtInterceptorProvider.whiteListedDomains setting to bypass the domain allowlist filter via a crafted domain. This is because the whiteListedDomains entries are treated as regular expressions. 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 wildcard which matches any character.

Recommendations For versions prior to 0.1.10, update to version 0.1.10 or later to resolve the issue. As a temporary workaround, consider manually validating domains against the allowlist to prevent bypassing the filter. Restrict access to the jwtInterceptorProvider.whiteListedDomains setting to minimize the risk of exploitation. Avoid using the whiteListedDomains setting with untrusted input until the issue is resolved.

Fix

RCE

Weakness Enumeration

CWE-20

Related Identifiers

CVE-2018-11537

GHSA-VM2P-F5J4-MJ6G

Affected Products

Angular-Jwt

References · 8

• https://osv.dev/vulnerability/CVE-2018-11537 · Vendor Advisory
• https://auth0.com/docs/security/bulletins/cve-2018-11537 · Vendor Advisory
• https://osv.dev/vulnerability/GHSA-vm2p-f5j4-mj6g · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2018-11537 · Security Note
• https://github.com/auth0/angular-jwt/commit/e368cf124443507f1710f60ae855c4c54eebc6ea · Note
• https://github.com/auth0/angular-jwt · Note
• https://github.com/auth0/angular-jwt/pull/174 · Note
• https://github.com/auth0/angular-jwt/commit/a4f03b49c3fb47cc6375c2a33b5ac11ca3c606f0 · Note