Authenticated token replay via unchecked JTI reuse
Published Apr 6, 2020 · Updated Aug 4, 2024
Authentication bypass in Ory Hydra before 1.4.0+oryOS.17 allows remote authenticated users to obtain access tokens by replaying private_key_jwt assertions. Hydra accepts repeated assertions because the OAuth2 token endpoint does not enforce uniqueness of the JWT jti claim. The attacker must first obtain a valid signed client assertion and replay it within its short expiry window; successful replay can issue additional bearer tokens and expose protected resources.
Summary
What happened
Authentication bypass in Ory Hydra before 1.4.0+oryOS.17 allows remote authenticated users to obtain access tokens by replaying private_key_jwt assertions. Hydra accepts repeated assertions because the OAuth2 token endpoint does not enforce uniqueness of the JWT jti claim. The attacker must first obtain a valid signed client assertion and replay it within its short expiry window; successful replay can issue additional bearer tokens and expose protected resources.
The record
- CVE
- CVE-2020-5300
- Published
- Apr 6, 2020
- Updated
- Aug 4, 2024
- Vendor
- Ory
- Product
- Hydra
- Classifications
- CWE-294
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 6, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.4.0+oryOS.17
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo