Date: Sun, 28 Jun 2020 13:52:19 +0000 (UTC) From: Matthias Andree <mandree@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r540715 - head/security/vuxml Message-ID: <202006281352.05SDqJU4056370@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: mandree Date: Sun Jun 28 13:52:19 2020 New Revision: 540715 URL: https://svnweb.freebsd.org/changeset/ports/540715 Log: security/putty: two security vulnerabilities in versions < 0.74 Security: 6190c0cd-b945-11ea-9401-2dcf562daa69 Security: CVE-2020-14002 Security: FZI-2020-5 Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Sun Jun 28 13:49:01 2020 (r540714) +++ head/security/vuxml/vuln.xml Sun Jun 28 13:52:19 2020 (r540715) @@ -58,6 +58,51 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> <vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">; + <vuln vid="6190c0cd-b945-11ea-9401-2dcf562daa69"> + <topic>PuTTY -- Release 0.74 fixes two security vulnerabilities</topic> + <affects> + <package> + <name>putty</name> + <range><lt>0.74</lt></range> + </package> + <package> + <name>putty-gtk2</name> + <range><lt>0.74</lt></range> + </package> + <package> + <name>putty-nogtk</name> + <range><lt>0.74</lt></range> + </package> + </affects> + <description> + <body xmlns="http://www.w3.org/1999/xhtml">; + <p>Simon Tatham reports:</p> + <blockquote cite="https://lists.tartarus.org/pipermail/putty-announce/2020/000030.html">; + <p>[Release 0.74] fixes the following security issues:</p> + <ul><li>New configuration option to disable PuTTY's default policy of + changing its host key algorithm preferences to prefer keys it + already knows. (There is a theoretical information leak in this + policy.) [CVE-2020-14002]</li> + <li>In some situations an SSH server could cause PuTTY to access freed + mdmory by pretending to accept an SSH key and then refusing the + actual signature. It can only happen if you're using an SSH agent.</li> + </ul> + </blockquote> + </body> + </description> + <references> + <url>https://lists.tartarus.org/pipermail/putty-announce/2020/000030.html</url>; + <url>https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/vuln-dynamic-hostkey-info-leak.html</url>; + <url>https://www.fzi.de/en/news/news/detail-en/artikel/fsa-2020-2-ausnutzung-eines-informationslecks-fuer-gezielte-mitm-angriffe-auf-ssh-clients/</url>; + <cvename>CVE-2020-14002</cvename> + <url>https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/vuln-agent-keylist-used-after-free.html</url>; + </references> + <dates> + <discovery>2020-06-27</discovery> + <entry>2020-06-28</entry> + </dates> + </vuln> + <vuln vid="6a5d15b6-b661-11ea-8015-e09467587c17"> <topic>chromium -- multiple vulnerabilities</topic> <affects>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202006281352.05SDqJU4056370>