OAuth token disclosure via plaintext log entries
Published Sep 23, 2022 · Updated May 22, 2025
Cleartext token logging in Rocket.Chat before 4.6.4 allows attackers to read OAuth access tokens from server logs. The OAuth integration writes returned access tokens into plaintext log entries without redacting the sensitive value. Exposure requires an OAuth flow that generates the entry and access to workspace or deployment logs; the disclosed consequence is token disclosure.
Summary
What happened
Cleartext token logging in Rocket.Chat before 4.6.4 allows attackers to read OAuth access tokens from server logs. The OAuth integration writes returned access tokens into plaintext log entries without redacting the sensitive value. Exposure requires an OAuth flow that generates the entry and access to workspace or deployment logs; the disclosed consequence is token disclosure.
The record
- CVE
- CVE-2022-32217
- Published
- Sep 23, 2022
- Updated
- May 22, 2025
- Vendor
- Rocket.Chat Technologies Corp.
- Product
- Rocket.Chat
- Classifications
- CWE-532, CWE-312, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 2022CVE publishedPublication date reported by the CVE source.
- May 22, 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=fixed in 4.6.4>
What conditions does exploitation require?
What is affected?
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