CVE-2020-5300CWE-294

Disallow replay of `private_key_jwt` by blacklisting JTIs in Hydra

Medium · published April 6, 2020

CVSS v3.1
5.8
EPSS
1%
Percentile
63.3
In the wild
Unconfirmed
What it is

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

The record
Technical detail
CVSS v3.1
5.8 · MEDIUM
Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N
CVSS v4.0
Not supplied
EPSS
0.01028 · 63.3th percentile
Weakness
CWE-294 · Authentication Bypass by Capture-replay
Published
2020-04-06T16:30Z
EPSS history
Timeline
  • 06 APR 16:30Z
    Disallow replay of `private_key_jwt` by blacklisting JTIs in Hydra
    cvelistv5