Skip to content

Exposure of sensitive Slack webhook URLs in debug logs and traces

High severity GitHub Reviewed Published Oct 9, 2022 in abdolence/slack-morphism-rust • Updated Feb 2, 2023

Package

cargo slack-morphism (Rust)

Affected versions

< 1.3.2

Patched versions

1.3.2

Description

Impact

Debug logs expose sensitive URLs for Slack webhooks that contain private information.

Patches

The problem is fixed in v1.3.2 which redacts sensitive URLs for webhooks.

Workarounds

Disabling/filtering debug logs in case you use Slack webhooks using tracing log level and filters.

References

https://github.com/abdolence/slack-morphism-rust/releases/tag/v1.3.2

For more information

If you have any questions or comments about this advisory:

References

@abdolence abdolence published to abdolence/slack-morphism-rust Oct 9, 2022
Published by the National Vulnerability Database Oct 10, 2022
Published to the GitHub Advisory Database Oct 10, 2022
Reviewed Oct 10, 2022
Last updated Feb 2, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.133%
(50th percentile)

Weaknesses

CVE ID

CVE-2022-39292

GHSA ID

GHSA-4mjx-2gh5-ph8h

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.