{"id":"CVE-2018-11537","published":"2018-06-19T19:00:00Z","modified":"2024-08-05T08:10:14Z","title":"Auth0 angular-jwt before 0.1.10 treats whiteListedDomains entries as regular expressions, which allows remote…","vendor":null,"product":null,"tier":"tail","description":{"text":"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 whitelist filter via a crafted domain.","provenance":"source","from":"CVE.org"},"cvss":null,"epss":{"score":0.01137,"percentile":0.67332,"provenance":"source"},"cwes":[],"references":[{"url":"https://auth0.com/docs/security/bulletins/cve-2018-11537","tags":["x_refsource_CONFIRM"]}],"priority":{"score":13.5,"factors":[{"name":"EPSS percentile","points":13.47}]},"affected":[{"ecosystem":"npm","package":"angular-jwt","vulnerableRanges":["<0.1.10"],"patched":["0.1.10"],"from":["GHSA-vm2p-f5j4-mj6g"],"provenance":"source"}],"summary":{"text":"The flaw is in the jwtInterceptorProvider.whiteListedDomains setting of Auth0's angular-jwt library, versions before 0.1.10, where whitelist entries are treated as regular expressions rather than literal domain names. An attacker who knows that the application uses this setting can craft a domain that matches the permissive pattern and bypass the domain whitelist filter.","provenance":"ai","model":"claude-haiku-5-5","generatedAt":"2026-11-20T21:54:57Z"},"euvd":{"id":"EUVD-2022-5377","exploited":false,"provenance":"source"}}