CVE-2020-5300
Hydra Private Key JWT JWT Reuse Vulnerability
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
INFO
Published Date :
April 6, 2020, 5:15 p.m.
Last Modified :
April 7, 2020, 1:52 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
4.0
Exploitability Score :
1.3
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2020-5300.
| URL | Resource |
|---|---|
| https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3 | Patch Third Party Advisory |
| https://github.com/ory/hydra/releases/tag/v1.4.0 | Third Party Advisory |
| https://github.com/ory/hydra/security/advisories/GHSA-3p3g-vpw6-4w66 | Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2020-5300 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2020-5300 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Apr. 07, 2020
Action Type Old Value New Value Added CVSS V2 NIST (AV:N/AC:M/Au:S/C:P/I:N/A:N) Added CVSS V3.1 NIST AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N Changed Reference Type https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3 No Types Assigned https://github.com/ory/hydra/commit/700d17d3b7d507de1b1d459a7261d6fb2571ebe3 Patch, Third Party Advisory Changed Reference Type https://github.com/ory/hydra/releases/tag/v1.4.0 No Types Assigned https://github.com/ory/hydra/releases/tag/v1.4.0 Third Party Advisory Changed Reference Type https://github.com/ory/hydra/security/advisories/GHSA-3p3g-vpw6-4w66 No Types Assigned https://github.com/ory/hydra/security/advisories/GHSA-3p3g-vpw6-4w66 Third Party Advisory Added CWE NIST CWE-294 Added CPE Configuration OR *cpe:2.3:a:ory:hydra:*:*:*:*:*:*:*:* versions up to (excluding) 1.4.0
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2020-5300 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2020-5300
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.10 }} 0.00%
score
0.39575
percentile