Date: Tue, 22 Feb 2022 13:47:01 GMT From: Dmitry Marakasov <amdmi3@FreeBSD.org> To: ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org Subject: git: 8ea19b1d123c - main - security/vuxml: py-tuf vulnerability Message-ID: <202202221347.21MDl1uW026848@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by amdmi3: URL: https://cgit.FreeBSD.org/ports/commit/?id=8ea19b1d123c53e92e544d1faccff9fe6b7327a1 commit 8ea19b1d123c53e92e544d1faccff9fe6b7327a1 Author: Dmitry Marakasov <amdmi3@FreeBSD.org> AuthorDate: 2022-02-22 13:45:17 +0000 Commit: Dmitry Marakasov <amdmi3@FreeBSD.org> CommitDate: 2022-02-22 13:46:41 +0000 security/vuxml: py-tuf vulnerability --- security/vuxml/vuln-2022.xml | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/security/vuxml/vuln-2022.xml b/security/vuxml/vuln-2022.xml index cf8aeb1457b1..5ff1b0674f91 100644 --- a/security/vuxml/vuln-2022.xml +++ b/security/vuxml/vuln-2022.xml @@ -1,3 +1,33 @@ + <vuln vid="85d976be-93e3-11ec-aaad-14dae9d5a9d2"> + <topic>The Update Framwork -- path traversal vulnerability</topic> + <affects> + <package> + <name>py37-tuf</name> + <name>py38-tuf</name> + <name>py39-tuf</name> + <name>py310-tuf</name> + <name>py311-tuf</name> + <range><le>0.18.1</le></range> + </package> + </affects> + <description> + <body xmlns="http://www.w3.org/1999/xhtml">; + <p>NVD reports:</p> + <blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2021-41131">; + <p>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. The file extension is always .json. A fix is available in version 0.19 or newer. There are no workarounds that do not require code changes. Clients can restrict the all owed 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.</p> + </blockquote> + </body> + </description> + <references> + <cvename>CVE-2021-41131</cvename> + <url>https://nvd.nist.gov/vuln/detail/CVE-2021-41131</url>; + </references> + <dates> + <discovery>2021-10-22</discovery> + <entry>2022-02-22</entry> + </dates> + </vuln> + <vuln vid="1cd565da-455e-41b7-a5b9-86ad8e81e33e"> <topic>seatd-launch -- remove files with escalated privileges with SUID</topic> <affects>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202202221347.21MDl1uW026848>