CVE-2020-5300
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…
Does this matter?
Lower severity and a low EPSS score (1.03%). Track it; it rarely justifies an emergency change on its own.
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
- CVSS 3.1
- 5.3 MEDIUMCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
- EPSS
- 1.03% probability · 62th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-294
- Affected
- ory/hydra
- Source
- security-advisories@github.com
References
- https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3Patch, Third Party Advisory
- https://github.com/ory/hydra/releases/tag/v1.4.0Third Party Advisory
- https://github.com/ory/hydra/security/advisories/GHSA-3p3g-vpw6-4w66Third Party Advisory
- https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3Patch, Third Party Advisory
- https://github.com/ory/hydra/releases/tag/v1.4.0Third Party Advisory
- https://github.com/ory/hydra/security/advisories/GHSA-3p3g-vpw6-4w66Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.