QID 980406

QID 980406: Python (pip) Security Update for tuf (GHSA-wjw6-2cqr-j4qr)

Security update has been released for tuf to fix the vulnerability.

Note: The preceding description block is extracted directly from the security advisory. Using automation, we have attempted to clean and format it as much as possible without introducing additional issues.

In both clients (`tuf/client` and `tuf/ngclient`), there is a path traversal vulnerability that in the worst case can overwrite files ending in `.json` anywhere on the client system on a call to `get_one_valid_targetinfo()`. It occurs because the rolename is used to form the filename, and may contain path traversal characters (ie `../../name.json`).

The impact is mitigated by a few facts:
* It only affects implementations that allow arbitrary rolename selection for delegated targets metadata
* The attack requires the ability to A) insert new metadata for the path-traversing role and B) get the role delegated by an existing targets metadata
* The written file content is heavily restricted since it needs to be a valid, signed targets file. The file extension is always .json.

CVSS V3 rated as Critical - 8.7 severity.

CVSS V2 rated as Critical - 8.8 severity.

Solution

A fix is available in version 0.19 or newer.Workaround:
None that do not require code changes. Clients can restrict the allowed character set for rolenames, or they can store metadata in files named in a way that is not vulnerable: neither of these approaches is possible without modifying python-tuf.

Vendor References

GHSA-wjw6-2cqr-j4qr - github.com/advisories/GHSA-wjw6-2cqr-j4qr

CVEs related to QID 980406

CVE-2021-41131 |

Software Advisories

Advisory ID	Software	Component	Link
GHSA-wjw6-2cqr-j4qr	tuf		github.com/advisories/GHSA-wjw6-2cqr-j4qr

By selecting these links, you may be leaving CVEreport webspace. We have provided these links to other websites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other websites that are more appropriate for your purpose. CVEreport does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, CVEreport does not endorse any commercial products that may be mentioned on these sites. Please address comments about any linked pages to [email protected].