CVE-2020-15222

HIGH EPSS 54.2%
Published Sep 24, 20205y ago · Modified Jun 17, 20262w ago
8.1 CVSS 3.1
High
Find Similar
Published Sep 24, 2020 5y ago
Last Modified Jun 17, 2026 2w ago

Description

In ORY Fosite (the security first OAuth2 & OpenID Connect framework for Go) before version 0.31.0, when using "private_key_jwt" authentication the uniqueness of the `jti` value is not checked. When using client authentication method "private_key_jwt", OpenId specification says the following about assertion `jti`: "A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties". Hydra does not seem to check the uniqueness of this `jti` value. This problem is fixed in version 0.31.0.

CVSS Details

Base Score
8.1
Exploitability
2.8
Impact
5.2
Vector string
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Attack Vector Network
Attack Complexity Low
Privileges Required None
User Interaction Required
Scope Unchanged
Confidentiality High
Integrity High
Availability None

Threat Intelligence

EPSS Exploit Probability
54.2% percentile
Exploit & Patch Status
Public Exploit Known
Patch Available

Weaknesses 2

CWE-287 Improper Authentication Authentication
CWE-345

Affected Products 1

VendorProductVersionRange
oryfosite* <0.31.0

References 3

  • github.com https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9
    PatchThird Party Advisory
  • github.com https://github.com/ory/fosite/security/advisories/GHSA-v3q9-2p3m-7g43
    ExploitThird Party Advisory
  • openid.net https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication
    Third Party Advisory

Remediation

  • github.com https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9
    PatchThird Party Advisory