Account takeover via predictable OAuth authorization codes
Published Aug 2, 2023 · Updated Aug 2, 2024
Weak authorization-code generation in OX App Suite backend 8.11 allows remote attackers to take over OAuth sessions via predicted codes. The integrated OAuth Authorization Service generates authorization codes with a source that lacks sufficient randomness, making the one-time codes predictable. The service is disabled by default; exposure requires the internal OAuth authorization server to be enabled, after which a predicted code can compromise another user's account.
Summary
What happened
Weak authorization-code generation in OX App Suite backend 8.11 allows remote attackers to take over OAuth sessions via predicted codes. The integrated OAuth Authorization Service generates authorization codes with a source that lacks sufficient randomness, making the one-time codes predictable. The service is disabled by default; exposure requires the internal OAuth authorization server to be enabled, after which a predicted code can compromise another user's account.
The record
- CVE
- CVE-2023-26451
- Published
- Aug 2, 2023
- Updated
- Aug 2, 2024
- Vendor
- Open-Xchange GmbH
- Product
- OX App Suite
- Classifications
- CWE-330, T1528
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 2, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=0 <=8.11
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