OAuth credential disclosure via derived Debug formatting
Published Jul 21, 2022 · Updated Apr 23, 2025
Sensitive-information exposure in Abdolence Slack Morphism for Rust before 0.41.0 allows attackers to disclose Slack OAuth secrets. OAuth listener configuration uses derived Debug formatting over raw String fields, causing formatted configurations to include secret values. Exposure requires an application to log OAuth requests, responses, or client configuration and attackers to obtain those logs; the reported consequence is credential disclosure.
Summary
What happened
Sensitive-information exposure in Abdolence Slack Morphism for Rust before 0.41.0 allows attackers to disclose Slack OAuth secrets. OAuth listener configuration uses derived Debug formatting over raw String fields, causing formatted configurations to include secret values. Exposure requires an application to log OAuth requests, responses, or client configuration and attackers to obtain those logs; the reported consequence is credential disclosure.
The record
- CVE
- CVE-2022-31162
- Published
- Jul 21, 2022
- Updated
- Apr 23, 2025
- Vendor
- Abdolence
- Product
- Slack Morphism for Rust
- Classifications
- CWE-212, CWE-1258, CWE-200, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 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=< 0.41.0
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