Slack bot compromise via unauthenticated token endpoints
Published Apr 26, 2024 · Updated Aug 2, 2024
Improper authorization in Onyx before 0.3.63 allows remote attackers to read and replace Slack bot tokens over the network. The GET and PUT handlers for /api/manage/admin/slack-bot/tokens call fetch_tokens and save_tokens without the current_admin_user dependency that enforces administrator access. Network reachability alone permits token disclosure or replacement, enabling control of the connected Slack bot and access to internal Slack data.
Summary
What happened
Improper authorization in Onyx before 0.3.63 allows remote attackers to read and replace Slack bot tokens over the network. The GET and PUT handlers for /api/manage/admin/slack-bot/tokens call fetch_tokens and save_tokens without the current_admin_user dependency that enforces administrator access. Network reachability alone permits token disclosure or replacement, enabling control of the connected Slack bot and access to internal Slack data.
The record
- CVE
- CVE-2024-32881
- Published
- Apr 26, 2024
- Updated
- Aug 2, 2024
- Vendor
- Onyx
- Product
- Onyx
- Classifications
- CWE-285, T1528, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 26, 2024CVE 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 <0.3.63
- Affected versionversion=< 0.3.63
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
- Unauthenticated Slack bot token endpoint proof of conceptproof of concept · demonstrated
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