CVE-2019-13483
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAuth0 Passport-SharePoint before 0.4.0 does not validate the JWT signature of an Access Token before processing. This allows attackers to forge tokens and bypass authentication and authorization mechanisms.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Auth0 Passport-SharePoint library before version 0.4.0 fails to validate JWT signatures on Access Tokens, allowing attackers to forge tokens and bypass authentication entirely. This critical validation gap enables unauthorized access to protected resources without proper credential verification.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify passport-sharepoint installationRun 'npm list passport-sharepoint' or check package.json for the passport-sharepoint dependencyAffected if The package is listed in dependencies and its version is below 0.4.0
-
Verify installed version numberRun 'npm list passport-sharepoint --depth=0' to see the exact version installed, or inspect node_modules/passport-sharePoint/package.json version fieldAffected if Version returned is less than 0.4.0 or no version is shown (indicating very old release)
-
Confirm SharePoint authentication is in useReview application source code for 'passport-sharepoint' require/import statements and verify the authentication strategy is being used with passport.use()Affected if The application code actively uses the passport-sharepoint strategy for authenticating users to SharePoint resources
-
Check JWT validation configurationInspect the passport-sharepoint configuration code for any token verification settings. Look for options passed to the strategy such as token validation callbacksAffected if No explicit JWT signature validation callback is configured, or the library's default behavior (which lacked validation) is being used
A user is affected if their application depends on passport-sharepoint version below 0.4.0 and uses it for SharePoint authentication, as tokens would not have their signatures validated.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data0.4.0
Upgrade Passport-SharePoint to version 0.4.0 or later which implements proper JWT signature validation. Verify all authentication flows work correctly after the upgrade.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13483 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-13483 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data