# CVE-2022-31162: Slack Morphism for Rust before 0.41.0 can accidentally leak Slack OAuth client information in application debug logs

> Slack Morphism for Rust leaks OAuth client secrets in debug logs, allowing attackers with log access to steal credentials.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-99j7-mhfh-w84p, RUSTSEC-2022-0086

## What is CVE-2022-31162?

CVE-2022-31162 is a high-severity vulnerability in abdolence slack-morphism-rust, published on 21 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Slack Morphism is an async client library for Rust. Prior to 0.41.0, it was possible for Slack OAuth client information to leak in application debug logs. Stricter and more secure debug formatting was introduced in v0.41.0 for OAuth secret types to reduce the possibility of printing sensitive information in application logs. As a workaround, do not print/output requests and responses for OAuth and client configurations in logs.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-1258 (Exposure of Sensitive System Information Due to Uncleared Debug Information)

## Which versions are affected by CVE-2022-31162?

3 open source packages ship an affected version, including slack-morphism. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `slack-morphism` | crates.io | All versions | 0.41.0 |
| `slack-morphism` | crates.io | All versions | 0.41.0 |
| `slack-morphism` | crates.io | From 0.0.0-0 | 0.41.0 |

Products: Slack Morphism Project Slack Morphism.

## How do I fix CVE-2022-31162?

Upgrade slack-morphism to 0.41.0 or later.

## Is CVE-2022-31162 being exploited?

There is no known exploitation of CVE-2022-31162 in the wild and no public exploit code.

## Other vulnerabilities in abdolence slack-morphism-rust

- [CVE-2022-39292](https://insights.sbomify.com/CVE-2022-39292/): Exposure of sensitive Slack webhook URLs in debug logs and traces (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31162 and fix it if it is affected.

What it is: CVE-2022-31162 is a high-severity vulnerability in abdolence slack-morphism-rust, published on 21 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-31162 in the wild and no public exploit code.

Affected packages and fixed versions:
- slack-morphism (crates.io): affected all versions; fixed in 0.41.0
- slack-morphism (crates.io): affected all versions; fixed in 0.41.0
- slack-morphism (crates.io): affected from 0.0.0-0; fixed in 0.41.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-31162/ (Markdown: https://insights.sbomify.com/CVE-2022-31162/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-31162
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-31162
- OSV: https://osv.dev/vulnerability/CVE-2022-31162

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-31162/
Summaries are generated and may contain mistakes; the official description above is the record.