Skip to content

Slack Morphism for Rust before 0.41.0 can leak Slack OAuth client information in application debug logs

High severity GitHub Reviewed Published Jul 16, 2022 in abdolence/slack-morphism-rust • Updated Jul 24, 2023

Package

cargo slack-morphism (Rust)

Affected versions

< 0.41.0

Patched versions

0.41.0

Description

Impact

Potential/accidental leaking of Slack OAuth client information in application debug logs.

Patches

More strict and secure debug formatting was introduced in v0.41 for OAuth secret types to avoid the possibility of printing sensitive information in application logs.

Workarounds

Don't print/output in logs request and responses for OAuth and client configurations.

For more information

If you have any questions or comments about this advisory:

References

@abdolence abdolence published to abdolence/slack-morphism-rust Jul 16, 2022
Published to the GitHub Advisory Database Jul 20, 2022
Reviewed Jul 20, 2022
Published by the National Vulnerability Database Jul 22, 2022
Last updated Jul 24, 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-31162

GHSA ID

GHSA-99j7-mhfh-w84p

Source code

Credits

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