Security readout for executives and security teams
Plain-English summary
Rust applications using Slack Morphism before 0.41.0 could accidentally write Slack OAuth client information into debug logs. The business risk is credential exposure through logs, not service outage. Urgency depends on whether affected applications used OAuth/client configuration logging and who can access those logs.
Executive priority
Prioritize remediation for applications handling Slack OAuth in environments with debug logging or broad log access. Treat confirmed log exposure as a credential-handling incident. If the library is absent, upgraded, or OAuth debug logging was never enabled, urgency is lower.
Technical view
The flaw is an information disclosure issue in slack-morphism-rust versions before 0.41.0. Debug formatting for OAuth secret types could reveal sensitive Slack OAuth client data in application logs. Version 0.41.0 introduced stricter debug formatting. CVSS is 7.5, confidentiality high, with no integrity or availability impact stated.
Likely exposure
Exposure is likely limited to Rust services that depend on slack-morphism-rust below 0.41.0 and log OAuth requests, responses, or client configurations at debug level. Risk increases where logs are centralized, broadly searchable, retained for long periods, or shared with third-party observability services.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not marked KEV. The practical risk is passive discovery of secrets already written to logs by authorized log users or anyone who later gains log access.
Researcher notes
Focus validation on dependency version, logging configuration, and log retention/access paths. The advisory names the workaround and the fixed version, but the provided sources do not describe public exploitation, affected downstream applications, or additional vendor-specific recovery steps.
Mitigation direction
- Upgrade slack-morphism-rust to version 0.41.0 or later.
- Stop logging OAuth requests, responses, and client configuration objects.
- Review vendor guidance for handling any confirmed exposed OAuth client information.
- Restrict access to application and centralized debug logs.
Validation and detection
- Inventory Rust dependencies for slack-morphism-rust versions below 0.41.0.
- Check whether affected services enable debug logging around Slack OAuth flows.
- Review relevant logs for exposed OAuth client information.
- Confirm upgraded builds use slack-morphism-rust 0.41.0 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1258: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-31162 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/abdolence/slack-morphism-rust/security/advisories/GHSA-99j7-mhfh-w84pCVE reference · x_refsource_CONFIRM
- https://github.com/abdolence/slack-morphism-rust/releases/tag/v0.41.0CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive System Information Due to Uncleared Debug Information
Exposure of Sensitive System Information Due to Uncleared Debug Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.