CVE-2015-2964
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 · uneditedNAMSHI | JOSE 5.0.0 and earlier allows remote attackers to bypass signature verification via crafted tokens in a JSON Web Tokens (JWT) header.
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 · moderate confidenceThe NAMSHI | JOSE library versions 5.0.0 and earlier contains a signature verification bypass vulnerability in its JWT (JSON Web Token) implementation. Attackers can craft malicious tokens in the JWT header that bypass the signature verification mechanism, allowing them to forge valid-seeming tokens and potentially authenticate as arbitrary users.
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<= 5.0.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
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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 the installed Namshi\Jose library versionCheck your project's composer.json or composer.lock file for the namshi/jose package version, or run 'composer show namshi/jose' to see the installed versionAffected if The installed version is 5.0.0 or any version earlier than the patched release (verify against the library's release history for version 5.0.1 or later)
-
Confirm JWT signature verification is in useSearch your codebase for calls to methods that perform JWT verification such as 'verify()', 'decode()' with signature validation, or any JWT validation logic that relies on the Namshi\Jose libraryAffected if Your application uses the Namshi\Jose library to verify JWT token signatures (the vulnerability only affects signature verification workflows)
-
Inspect how JWT tokens are processedReview the code that handles incoming JWT tokens and passes them to the library for validation; examine the token header parsing logicAffected if Your application accepts and processes JWT tokens from untrusted sources (such as user authentication headers) using the affected library
-
Review token validation configurationCheck if your JWT validation implementation includes any secondary validation checks such as issuer (iss) claim validation, audience (aud) claim validation, or token expiration checks; also review whether token blacklisting is implementedAffected if Your validation relies solely on the library's signature verification without additional claim validation layers (the vulnerability allows signature bypass, making secondary checks critical for detection)
You are affected if your application uses Namshi\Jose version 5.0.0 or earlier for JWT signature verification and does not implement additional validation checks beyond the library's signature verification.
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 dataUpgrade to a patched version of NAMSHI | JOSE. Additionally, implement secondary validation checks such as expected issuer/audience claims verification and consider implementing token blacklisting for compromised tokens.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2964 — 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-2015-2964 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