CVSS: 8.8EPSS: 0%CPEs: 1EXPL: 0CVE-2021-41131 – Client metadata path-traversal in python-tuf
https://notcve.org/view.php?id=CVE-2021-41131
python-tuf is a Python reference implementation of The Update Framework (TUF). 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. • https://github.com/theupdateframework/python-tuf/commit/4ad7ae48fda594b640139c3b7eae21ed5155a102 https://github.com/theupdateframework/python-tuf/issues/1527 https://github.com/theupdateframework/python-tuf/security/advisories/GHSA-wjw6-2cqr-j4qr • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •
CVSS: 8.7EPSS: 0%CPEs: 1EXPL: 0CVE-2020-15163 – Invalid root may become trusted root in The Update Framework (TUF)
https://notcve.org/view.php?id=CVE-2020-15163
Python TUF (The Update Framework) reference implementation before version 0.12 it will incorrectly trust a previously downloaded root metadata file which failed verification at download time. This allows an attacker who is able to serve multiple new versions of root metadata (i.e. by a person-in-the-middle attack) culminating in a version which has not been correctly signed to control the trust chain for future updates. This is fixed in version 0.12 and newer. Una implementación de referencia de Python TUF (The Update Framework) anterior a la versión 0.12, confiará incorrectamente en un archivo de metadatos root descargado previamente que presentó un fallo al verificar en el momento de la descarga. Esto permite a un atacante que es capaz servir múltiples versiones nuevas de metadatos root (es decir, mediante un ataque de tipo person-in-the-middle) culminar en una versión que no ha sido firmada correctamente para controlar la cadena de confianza de futuras actualizaciones. • https://github.com/theupdateframework/tuf/commit/3d342e648fbacdf43a13d7ba8886aaaf07334af7 https://github.com/theupdateframework/tuf/pull/885 https://github.com/theupdateframework/tuf/releases/tag/v0.12.0 https://github.com/theupdateframework/tuf/security/advisories/GHSA-f8mr-jv2c-v8mg https://pypi.org/project/tuf • CWE-345: Insufficient Verification of Data Authenticity CWE-863: Incorrect Authorization •
CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 0CVE-2020-6174
https://notcve.org/view.php?id=CVE-2020-6174
TUF (aka The Update Framework) through 0.12.1 has Improper Verification of a Cryptographic Signature. TUF (también se conoce como The Update Framework) versiones hasta 0.12.1, presenta una Comprobación Inapropiada de una Firma Criptográfica. • https://github.com/theupdateframework/tuf/pull/974 • CWE-347: Improper Verification of Cryptographic Signature •
CVSS: 5.3EPSS: 0%CPEs: 1EXPL: 1CVE-2020-6173
https://notcve.org/view.php?id=CVE-2020-6173
TUF (aka The Update Framework) 0.7.2 through 0.12.1 allows Uncontrolled Resource Consumption. TUF (también se conoce como The Update Framework) versiones 0.7.2 hasta 0.12.1, permite un Consumo de Recursos No Controlados. • https://github.com/theupdateframework/tuf/commits/develop https://github.com/theupdateframework/tuf/issues/973 • CWE-400: Uncontrolled Resource Consumption •