dbcve.org
Slack MorphismApplication · Slack Morphism Project

CVE-2022-39292

HIGH · 7.5 CVSS v3.1 Published 2022-10-10
Fix available
A fix is available. Upgrade to after 1.3.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 a modern client library for Slack Web/Events API/Socket Mode and Block Kit. Debug logs expose sensitive URLs for Slack webhooks that contain private information. The problem is fixed in version 1.3.2 which redacts sensitive URLs for webhooks. As a workaround, people who use Slack webhooks may disable or filter debug 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 library versions before 1.3.2 expose sensitive Slack webhook URLs (containing private tokens/identifiers) in debug logs. This creates an information disclosure vulnerability where sensitive authentication credentials could be captured in log files.

MitigationUpgrade to Slack Morphism version 1.3.2 or later which implements URL redaction for webhooks. As a temporary workaround, disable or filter debug logging to prevent exposure of sensitive URLs.

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:<= 1.3.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 installed Slack Morphism version
    Run a package manager query to retrieve the installed version. For npm: 'npm list slack-morphism'. For Rust/Cargo: 'cargo tree -p slack-morphism'. For Maven: check the pom.xml or dependency tree. Compare the version number against the affected range <= 1.3.0.
    Affected if The installed version is 1.3.0 or lower.
  2. Verify debug logging is enabled
    Review your application's logging configuration (logback.xml, log4j.properties, logging.yaml, or similar) and runtime settings. Look for debug-level logging configured for the Slack Morphism library or its parent package.
    Affected if Debug-level logging is enabled for the library.
  3. Search application logs for webhook URLs
    Search log files for patterns matching Slack webhook URLs. Look for strings containing 'slack.com/services/' or 'hooks.slack.com' combined with tokens (alphanumeric strings after the path). Use grep or similar: grep -r 'hooks.slack.com' /path/to/logs
    Affected if Log files contain unredacted Slack webhook URLs with visible token or identifier segments.
  4. Inspect recent log files for sensitive URL fragments
    Examine the most recent application log files (especially debug-level logs) for any webhook URL patterns. Check both application logs and system logs if the library logs to stdout/stderr.
    Affected if Debug logs contain Slack webhook URLs that expose path segments resembling authentication tokens.

You are affected if you have Slack Morphism version 1.3.0 or earlier installed AND debug logging is active AND your log files contain unredacted Slack webhook URLs with visible token identifiers.

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 a release after 1.3.0
Interim mitigation

Upgrade to Slack Morphism version 1.3.2 or later which implements URL redaction for webhooks. As a temporary workaround, disable or filter debug logging to prevent exposure of sensitive URLs.

Recommended fix High confidence

1.3.2

  1. Upgrade Slack Morphism library from any version <= 1.3.0 to version 1.3.2 or later

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39292 — 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-39292 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