Advisory Database
  • Advisories
  • Dependency Scanning
  1. maven
  2. ›
  3. org.pac4j/pac4j-core
  4. ›
  5. CVE-2021-44878

CVE-2021-44878: Token validation bypass in Pac4j

January 8, 2022

Pac4j v5.1 and earlier allows (by default) clients to accept and successfully validate ID Tokens with “none” algorithm (i.e., tokens with no signature) which is not secure and violates the OpenID Core Specification. The “none” algorithm does not require any signature verification when validating the ID tokens, which allows the attacker to bypass the token validation by injecting a malformed ID token using “none” as the value of “alg” key in the header with an empty signature value.

References

  • github.com/advisories/GHSA-xhw6-hjc9-679m
  • github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae
  • nvd.nist.gov/vuln/detail/CVE-2021-44878

Code Behaviors & Features

Detect and mitigate CVE-2021-44878 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 5.2.0

Fixed versions

  • 5.2.0

Solution

Upgrade to version 5.2.0 or above.

Impact 7.5 HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Learn more about CVSS

Source file

maven/org.pac4j/pac4j-core/CVE-2021-44878.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 14 May 2025 12:15:52 +0000.