Skip to content

Improper sanitization of delegated role names

High severity GitHub Reviewed Published Oct 19, 2021 in awslabs/tough • Updated Feb 1, 2023

Package

cargo tough (Rust)

Affected versions

< 0.12.0

Patched versions

0.12.0

Description

Impact

The tough library, prior to 0.12.0, does not properly sanitize delegated role names when caching a repository, or when loading a repository from the filesystem. When the repository is cached or loaded, files ending with the .json extension could be overwritten with role metadata anywhere on the system.

AWS would like to thank https://github.com/jku for reporting this issue.

Patches

A fix is available in version 0.12.0.

Workarounds

No workarounds to this issue are known.

References

GHSA-wjw6-2cqr-j4qr

References

@webern webern published to awslabs/tough Oct 19, 2021
Reviewed Oct 19, 2021
Published by the National Vulnerability Database Oct 19, 2021
Published to the GitHub Advisory Database Oct 19, 2021
Last updated Feb 1, 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
High
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
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:H/PR:L/UI:N/S:C/C:H/I:H/A:N

EPSS score

0.067%
(31st percentile)

Weaknesses

CVE ID

CVE-2021-41150

GHSA ID

GHSA-r56q-vv3c-6g9c

Source code

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