Sensitive URL exposure via debug logging
Published Oct 10, 2022 · Updated Apr 23, 2025
Information disclosure in Abdolence Slack Morphism for Rust 1.3.0 and earlier allows remote attackers to read private webhook URLs via debug logs. The SlackClientHyperConnector logged request.uri() without redacting sensitive webhook paths; the fix replaces the full URI with a redacted path and a hash. Exploitation requires an application to use Slack webhooks with debug logging enabled, and anyone able to read those logs can obtain the private URL values.
Summary
What happened
Information disclosure in Abdolence Slack Morphism for Rust 1.3.0 and earlier allows remote attackers to read private webhook URLs via debug logs. The SlackClientHyperConnector logged request.uri() without redacting sensitive webhook paths; the fix replaces the full URI with a redacted path and a hash. Exploitation requires an application to use Slack webhooks with debug logging enabled, and anyone able to read those logs can obtain the private URL values.
The record
- CVE
- CVE-2022-39292
- Published
- Oct 10, 2022
- Updated
- Apr 23, 2025
- Vendor
- Abdolence
- Product
- Slack Morphism for Rust
- Classifications
- CWE-1258
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 10, 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=<= 1.3.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