Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Packagist package

lcobucci/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 4.4PackagistPublished

    File reference keys leads to incorrect hashes on HMAC algorithms

    CVE-2021-41106 · GHSA-7322-jrq4-x5hf

    Affected
    • Packagist lcobucci/jwt >= 3.4.0, < 3.4.6; >= 4.0.0, < 4.0.4; >= 4.1.0, < 4.1.5
    Fixed in
    4.1.53.4.64.0.4· Vendor fix available
    Issue
    Impact Users of HMAC-based algorithms (HS256, HS384, and HS512) combined with Lcobucci\JWT\Signer\Key\LocalFileReference as key are having their tokens issued/validated using the file path as hashing key - instead of the contents. The HMAC hashing functions take any string as input and, since users can issue and validate tokens, people are lead to believe that everything works properly. Patches All versions have been patched to always load the file contents, deprecated the Lcobucci\JWT\Signer\Key\LocalFileReference, and suggest Lcobucci\JWT\Signer\Key\InMemory as the alternative. Workarounds Use Lcobucci\JWT\Signer\Key\InMemory instead of Lcobucci\JWT\Signer\Key\LocalFileReference to create the instances of your keys:

    Recommended action: Upgrade to 4.1.5, 4.0.4 or 3.4.6 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →