Unauthenticated access via unawaited token verification
Published May 31, 2022 · Updated Apr 23, 2025
Authentication bypass in Raman Chat Server 2.3.2 through versions before 2.6.0 allows remote attackers to authenticate with invalid access tokens. The access-key handler calls the asynchronous this.authProvider.verifyAccessKey function without await, so its try block returns HTTP 200 before a rejected verification promise reaches the catch block. No credentials or user interaction are required, and operations protected solely by this check accept an invalid token.
Summary
What happened
Authentication bypass in Raman Chat Server 2.3.2 through versions before 2.6.0 allows remote attackers to authenticate with invalid access tokens. The access-key handler calls the asynchronous this.authProvider.verifyAccessKey function without await, so its try block returns HTTP 200 before a rejected verification promise reaches the catch block. No credentials or user interaction are required, and operations protected solely by this check accept an invalid token.
The record
- CVE
- CVE-2022-31013
- Published
- May 31, 2022
- Updated
- Apr 23, 2025
- Vendor
- Raman
- Product
- Chat Server
- Classifications
- CWE-287, CWE-20, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 31, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=>= 2.3.2, < 2.6.0
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