Vulnerability · Published Apr 6, 2020 · Assigned by GitHub_M

CVE-2020-5300Disallow replay of `private_key_jwt` by blacklisting JTIs in Hydra

Medium 5.8

In plain English

A medium-severity security flaw in hydra from ory. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 1.0% (higher than 64% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.8Medium
Exploit odds (30 days)1.0%top 36.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In Hydra (an OAuth2 Server and OpenID Certified™ OpenID Connect Provider written in Go), before version 1.4.0+oryOS.17, when using client authentication method 'private_key_jwt' [1], 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 check the uniqueness of this `jti` value. Exploiting this vulnerability is somewhat difficult because: - TLS protects against MITM which makes it difficult to intercept valid tokens for replay attacks - The expiry time of the JWT gives only a short window of opportunity where it could be replayed This has been patched in version v1.4.0+oryOS.17

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogithub.com/ory/hydra1.4.0GHSA-3p3g-vpw6-4w66
Gogithub.com/ory/hydra1.4.0GO-2022-0786

Affected products (as reported)

VendorProductVersions
ory hydra < 1.4.0+oryOS.17

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

References