Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

angular-jwt

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5npmAmendedPublished

    Auth0 angular-jwt misinterprets allowlist as regex

    CVE-2018-11537 · GHSA-vm2p-f5j4-mj6g

    Affected
    • npm angular-jwt < 0.1.10
    Fixed in
    0.1.10· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 0.1.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →