Is CVE-2020-5300 actively exploited?

CVE-2020-5300 has no public evidence of in-the-wild exploitation as of 2024-11-21.

What is the CVSS score for CVE-2020-5300?

CVE-2020-5300 has a CVSS score of 5.8 (MEDIUM severity). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N.

How do I patch CVE-2020-5300?

Patch guidance is available from ory security advisories. CVEDatabase generates AI-assisted remediation guidance on demand for CVE-2020-5300.

CVE-2020-5300 - remediation guidance & executive summary

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 Metrics

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N
Attack Vector: network
Complexity: high
Privileges: low
User Action: required
Scope: changed
Confidentiality: high
Integrity: none
Availability: none
Weaknesses: CWE-294 CWE-294

Metadata

Primary Vendor: ORY
Published: 4/6/2020
Last Modified: 11/21/2024
Source: NIST NVD
Note: Verify all details with official vendor sources before applying patches.

Affected Products

ory : hydra

Remediation Guidance

Executive Summary

Cite this page

CVE-2020-5300. CVEDatabase.com. Retrieved 1 May 2026. https://cvedatabase.com/cve/CVE-2020-5300

View on NIST NVD

CVE-2020-5300 vulnerability