CVE-2020-5300
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2020-5300
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2020-5300.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2020-5300
- Aliases
- Related
- Published
- 2020-04-06T17:15:13Z
- Modified
- 2025-01-08T10:32:33.647574Z
- Severity
-
- 5.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N CVSS Calculator
- Summary
- [none]
- Details
-
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 'privatekeyjwt' [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 thisjtivalue. 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 - References
Affected packages
Git / github.com/ory/hydra
Affected ranges
- Type
- GIT
- Repo
- https://github.com/ory/hydra
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixedFixed