Vulnerability · Published Sep 24, 2020 · Assigned by GitHub_M

CVE-2020-15222Replay of private_key_jwt possible in ORY Fosite

High 8.1

In plain English

A high-severity improper authentication in fosite from ory. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.9% (higher than 59% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)8.1High
Exploit odds (30 days)0.9%top 41.1% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogithub.com/ory/fosite0.31.0GHSA-v3q9-2p3m-7g43
Gogithub.com/ory/fosite0.31.0GO-2021-0110

Affected products (as reported)

VendorProductVersions
ory fosite < 0.31.0

Weakness: CWE-287 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

References