Authentication bypass via shared persistent-cookie signing key
Published Jan 30, 2020 · Updated Aug 4, 2024
Authentication bypass in Opencast before 7.6 and version 8.0 allows remote attackers with a stolen persistent-login token to access peer servers. The default etc/security/mh_default_org.xml configuration signs persistent-cookie data with the same hard-coded system key on every server. Exploitation requires a valid token from another account and identical account credentials across targets; it grants access to peer cluster nodes without revealing the password.
Summary
What happened
Authentication bypass in Opencast before 7.6 and version 8.0 allows remote attackers with a stolen persistent-login token to access peer servers. The default etc/security/mh_default_org.xml configuration signs persistent-cookie data with the same hard-coded system key on every server. Exploitation requires a valid token from another account and identical account credentials across targets; it grants access to peer cluster nodes without revealing the password.
The record
- CVE
- CVE-2020-5222
- Published
- Jan 30, 2020
- Updated
- Aug 4, 2024
- Vendor
- Opencast
- Product
- Opencast
- Classifications
- CWE-798, T1550.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 30, 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=< 7.6
- Affected versionversion=>= 8.0, < 8.1
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