CVE-2021-41149: Tough Improper Sanitization Of Target Names Vulnerability

HIGH
Advisory Identifier: GHSA-x3r5-q6mj-m485
Share
CVSS 8.2
CWE-22
Published
Advisory Summary

CVE-2021-41149 is a HIGH (CVSS 8.2) improper sanitization of target names vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Tough libraries in the crates.io ecosystem. The issue involves improper sanitization of target names. Remediation is available by upgrading affected packages to version 0.12.0.

CVE-2021-41149 at a Glance

CVE Identifier CVE-2021-41149
GHSA Identifier GHSA-x3r5-q6mj-m485
Severity HIGH
CVSS v3.1 Base Score 8.2
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Tough
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 8.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2021-41149

To remediate this vulnerability, upgrade all affected Tough dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

tough fixed: 0.12.0 
Upgrade tough to 0.12.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for tough

How to Check if You Are Affected

To determine whether your application is affected by CVE-2021-41149, inspect your project dependencies for Tough:

inspect dependencies for tough

Analyze the terminal output to locate any version of Tough in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.12.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Tough, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact The tough library, prior to 0.12.0, does not properly sanitize target names when caching a repository, or when saving specific targets to an output directory. When targets are cached or saved, files could be overwritten with arbitrary content 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.

CVE-2021-41149 Affected Tough Versions

1 component(s)
Fixed Versions:
0.12.0
Product / Package Ecosystem Affected Versions Fixed Version
tough
 crates.io
< 0.12.0
0.12.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/awslabs/tough/security/advisories/GHSA-x3r5-q6mj-m485
NVD — CVE-2021-41149 NVD
https://nvd.nist.gov/vuln/detail/CVE-2021-41149
Security Fix Commit FIX COMMIT
https://github.com/awslabs/tough/commit/1809b9bd1106d78a51fbea3071aa97a3530bac9a
Tough Source Repository REPOSITORY
https://github.com/awslabs/tough

Frequently Asked Questions

What is CVE-2021-41149?
CVE-2021-41149 is a security vulnerability in Tough involving Improper sanitization of target names under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Tough versions are affected?
Affected versions include releases prior to 0.12.0 across affected packages: tough.
What version fixes CVE-2021-41149?
Upgrading to 0.12.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is tough affected?
Yes, tough is affected in releases prior to 0.12.0. Upgrade your dependency to 0.12.0 or later.
What is the CVSS score of CVE-2021-41149?
CVE-2021-41149 has a CVSS v3.1 base score of 8.2 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N.
What CWE is associated with CVE-2021-41149?
CVE-2021-41149 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check crates.io dependencies for CVE-2021-41149?
Run the dependency tree command: 'inspect dependencies for tough'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-x3r5-q6mj-m485",
  "modified" : "2021-10-19T18:04:34Z",
  "published" : "2021-10-19T20:16:15Z",
  "aliases" : [ "CVE-2021-41149" ],
  "summary" : "Improper sanitization of target names",
  "details" : "### Impact\nThe tough library, prior to 0.12.0, does not properly sanitize target names when caching a repository, or when saving specific targets to an output directory. When targets are cached or saved, files could be overwritten with arbitrary content anywhere on the system.\n\nAWS would like to thank https://github.com/jku for reporting this issue.\n\n### Patches\nA fix is available in version 0.12.0.\n\n### Workarounds\nNo workarounds to this issue are known.\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "tough"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.12.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/awslabs/tough/security/advisories/GHSA-x3r5-q6mj-m485"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2021-41149"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/awslabs/tough/commit/1809b9bd1106d78a51fbea3071aa97a3530bac9a"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/awslabs/tough"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-10-19T18:04:34Z",
    "nvd_published_at" : "2021-10-19T18:15:00Z"
  }
}