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

High 8.1 Published Updated

Attackers can replay private_key_jwt assertions in ORY Fosite due to missing jti uniqueness checks, bypassing authentication protections.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2020-15222?

CVE-2020-15222 is a high-severity vulnerability in ory fosite, published on 24 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

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.

Weakness: CWE-345, CWE-287

Which versions are affected by CVE-2020-15222?

3 open source packages ship an affected version, including github.com/ory/fosite. It affects 1 product.

PackageAffectedFixed in
github.com/ory/fosite GoAll versions0.31.0
github.com/ory/fosite GoAll versions0.31.0
github.com/ory/fosite GoAll versions0.31.0

Products include Ory Fosite.

How do I fix CVE-2020-15222?

Upgrade github.com/ory/fosite to 0.31.0 or later.

Is CVE-2020-15222 being exploited?

There is no known exploitation of CVE-2020-15222 in the wild and no public exploit code.

Sources

Also known as GHSA-v3q9-2p3m-7g43, GO-2021-0110.

Is CVE-2020-15222 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free