Skip to content

← Public intelligence

Packagist package

lexik/jwt-authentication-bundle

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

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

  1. UnratedPackagistPublished

    User enumeration in authentication mechanisms

    GHSA-2frx-j9hj-6c65

    Affected
    • Packagist lexik/jwt-authentication-bundle < 2.10.7; >= 2.11.0, < 2.11.3
    Fixed in
    2.11.32.10.7· Vendor fix available
    Issue
    ----------- The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. Resolution ---------- We now ensure that a generic message is returned whether the user exists or not if the password is invalid or if the user does not exist. The patch for this issue is available here for branch 2.10.x and 2.x. Credits ------- I would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.

    Recommended action: Upgrade to 2.11.3 or 2.10.7 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 →
  2. Medium, CVSS 5.3PackagistPublished

    Prevent user enumeration using Guard or the new Authenticator-based Security

    CVE-2021-21424 · GHSA-5pv8-ppvj-4h68

    Affected
    • Packagist lexik/jwt-authentication-bundle >= 2.0.0, < 2.10.7; >= 2.11.0, < 2.11.3
    Fixed in
    2.11.32.10.7· Vendor fix available
    Issue
    ----------- The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user. Resolution ---------- We now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist. The patch for this issue is available here for branch 3.4. Credits ------- I would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.

    Recommended action: Upgrade to 2.11.3 or 2.10.7 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 →