dbcve.org
Slack MorphismApplication · Slack Morphism Project

CVE-2022-31162

HIGH · 7.5 CVSS v3.1 Published 2022-07-22
Fix available
A fix is available. Upgrade to 0.41.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Slack Morphism versions before 0.41.0 had insecure debug formatting for OAuth secret types, causing sensitive client credentials (client IDs, client secrets, tokens) to be inadvertently logged when debug logging was enabled. This exposes OAuth authentication secrets in application logs, potentially allowing attackers who gain access to logs to impersonate the application.

MitigationUpgrade Slack Morphism library to version 0.41.0 or later which implements secure debug formatting. As a workaround, ensure OAuth and client configuration data is never printed or logged.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Slack MorphismApplication
Affected:< 0.41.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Slack Morphism library version
    Check your project's dependency file (pom.xml, build.gradle, package.json, Cargo.toml, etc.) for the slack-morphism or com.hubspot.slack-morphism dependency version
    Affected if The version listed is below 0.41.0 (e.g., 0.40.0, 0.30.1, etc.)
  2. Verify debug logging is enabled
    Review your application configuration files (application.properties, application.yml, logback.xml, log4j.xml, or environment variables) for debug-level logging configuration related to Slack Morphism or OAuth components
    Affected if Debug logging is explicitly enabled for Slack Morphism classes or the broader application logger that would capture OAuth operations
  3. Inspect application logs for credential exposure
    Search your application log files or log aggregation system for patterns matching OAuth client IDs, client secrets, or tokens that correspond to your Slack app configuration
    Affected if Any OAuth credentials (client_id, client_secret, access_token, or similar patterns) appear in plaintext within log output
  4. Check code for OAuth object logging
    Search your codebase for instances where OAuthConfig, ClientCredentials, or similar Slack Morphism client objects are passed to logging statements (e.g., logger.debug(), logger.info()) or toString() methods
    Affected if OAuth configuration objects are being logged or printed, especially at debug level

You are affected if Slack Morphism version is below 0.41.0 AND debug logging is enabled AND OAuth credentials appear in your application logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.41.0 or later
Fixed in 0.41.0
Interim mitigation

Upgrade Slack Morphism library to version 0.41.0 or later which implements secure debug formatting. As a workaround, ensure OAuth and client configuration data is never printed or logged.

Recommended fix High confidence

0.41.0

  1. Update the Slack Morphism dependency in Cargo.toml to version 0.41.0 or later (e.g., slack_morphism = "0.41.0")
  2. Run cargo update to fetch the new dependency version
  3. Rebuild the application with cargo build
  4. Verify OAuth functionality still works correctly in the application
  5. Ensure debug logs are not printing OAuth client secrets or sensitive configuration data
Caveat Debug formatting for OAuth secret types was changed to be stricter and more secure - any code relying on specific debug output format for these types will need updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Slack Morphism Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31162 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31162 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data