CVE-2020-15240

unknown
Published 2020-11-03 ยท Modified 2026-03-13
CVSS v3
โ€”
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
โ€”

Description

omniauth-auth0 (rubygems) versions >= 2.3.0 and < 2.4.1 improperly validate the JWT token signature when using the `jwt_validator.verify` method. Improper validation of the JWT token signature can allow an attacker to bypass authentication and authorization. You are affected by this vulnerability if all of the following conditions apply: 1. You are using `omniauth-auth0`. 2. You are using `JWTValidator.verify` method directly OR you are not authenticating using the SDKโ€™s default Authorization Code Flow. The issue is patched in version 2.4.1.

Predictions

Exploit likelihood
30%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

debian Debian Fixed 1 release
VersionStatusFixed in
bullseye Fixed 0

Package impact

EcosystemPackageVulnerableFixed
ruby RubyGemsomniauth-auth0!< 2.3.0||<>= 2.4.1>= 2.4.1
ruby RubyGemsomniauth-auth0>=2.3.0,<2.4.12.4.1

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.