GHSA-4rr6-gf59-ggw5: Namshi/jose Namshi/jose - Verification Bypass Vulnerability

CRITICAL
Published
Advisory Summary

GHSA-4rr6-gf59-ggw5 is a CRITICAL namshi/jose - verification bypass vulnerability (General Security Weakness) affecting Namshi/jose libraries in the Packagist ecosystem. The issue involves namshi/jose - verification bypass. Remediation is available by upgrading affected packages to version 2.2.0.

GHSA-4rr6-gf59-ggw5 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-4rr6-gf59-ggw5
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Namshi/jose
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix GHSA-4rr6-gf59-ggw5

To remediate this vulnerability, upgrade all affected Namshi/jose dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

namshi/jose fixed: 2.2.0
Upgrade namshi/jose to 2.2.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for namshi/jose

How to Check if You Are Affected

To determine whether your application is affected by GHSA-4rr6-gf59-ggw5, inspect your project dependencies for Namshi/jose:

inspect dependencies for namshi/jose

Analyze the terminal output to locate any version of Namshi/jose in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.2.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Namshi/jose, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Several widely-used JSON Web Token (JWT) libraries, including node-jsonwebtoken, pyjwt, namshi/jose, php-jwt, and jsjwt, are affected by critical vulnerabilities that could allow attackers to bypass the verification step when using asymmetric keys (RS256, RS384, RS512, ES256, ES384, ES512).

GHSA-4rr6-gf59-ggw5 Affected Namshi/jose Versions

1 component(s)
Fixed Versions:
2.2.0
Product / Package Ecosystem Affected Versions Fixed Version
namshi/jose
Packagist
< 2.2.0
2.2.0

References

Frequently Asked Questions

What is GHSA-4rr6-gf59-ggw5?
GHSA-4rr6-gf59-ggw5 is a security vulnerability in Namshi/jose involving namshi/jose - Verification bypass under General Security Weakness.
Which Namshi/jose versions are affected?
Affected versions include releases prior to 2.2.0 across affected packages: namshi/jose.
What version fixes GHSA-4rr6-gf59-ggw5?
Upgrading to 2.2.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is namshi/jose affected?
Yes, namshi/jose is affected in releases prior to 2.2.0. Upgrade your dependency to 2.2.0 or later.
What CWE is associated with GHSA-4rr6-gf59-ggw5?
GHSA-4rr6-gf59-ggw5 is classified under General Security Weakness.
How can I check Packagist dependencies for GHSA-4rr6-gf59-ggw5?
Run the dependency tree command: 'inspect dependencies for namshi/jose'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4rr6-gf59-ggw5",
  "modified" : "2024-05-17T22:31:44Z",
  "published" : "2024-05-17T22:31:44Z",
  "aliases" : [ ],
  "summary" : "namshi/jose - Verification bypass",
  "details" : "Several widely-used JSON Web Token (JWT) libraries, including node-jsonwebtoken, pyjwt, namshi/jose, php-jwt, and jsjwt, are affected by critical vulnerabilities that could allow attackers to bypass the verification step when using asymmetric keys (RS256, RS384, RS512, ES256, ES384, ES512).",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "namshi/jose"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.2.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries"
  }, {
    "type" : "WEB",
    "url" : "https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/namshi/jose/2015-03-10.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/namshi/jose"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-05-17T22:31:44Z",
    "nvd_published_at" : null
  }
}