Rocket.Chat: OAuth access and refresh tokens remain valid after account deactivation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Rocket.Chat is an open-source, secure, fully customizable communications platform. Prior to 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12, Rocket.Chat does not revoke OAuth bearer or refresh tokens when a user is deactivated. A deactivated user can continue using an existing OAuth access token, and can also mint a fresh access token from an existing refresh token. This vulnerability is fixed in 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- RocketChat Rocket.Chat
From 8.5.0-rc.0 · fixed in 8.5.0; From 8.4.0-rc.0 · fixed in 8.4.2; From 8.3.0-rc.0 · fixed in 8.3.4; From 8.2.0-rc.0 · fixed in 8.2.4; From 8.1.0-rc.0 · fixed in 8.1.5; From 8.0.0-rc.0 · fixed in 8.0.6; From 7.11.0-rc.0 · fixed in 7.13.8; fixed in 7.10.12