Date: Thu, 27 Jun 2019 21:05:55 +0000 (UTC) From: Palle Girgensohn <girgen@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r505244 - head/security/vuxml Message-ID: <201906272105.x5RL5tA2061561@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: girgen Date: Thu Jun 27 21:05:55 2019 New Revision: 505244 URL: https://svnweb.freebsd.org/changeset/ports/505244 Log: Add vuxml entry for postgresql lt 10.9 and lt 11.4 Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Thu Jun 27 20:18:20 2019 (r505243) +++ head/security/vuxml/vuln.xml Thu Jun 27 21:05:55 2019 (r505244) @@ -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="245629d4-991e-11e9-82aa-6cc21735f730"> + <topic>PostgreSQL -- Stack-based buffer overflow via setting a password</topic> + <affects> + <package> + <name>postgresql11-server</name> + <range><lt>11.4</lt></range> + </package> + <package> + <name>postgresql10-server</name> + <range><lt>10.9</lt></range> + </package> + </affects> + <description> + <body xmlns="http://www.w3.org/1999/xhtml">; + <p>The PostgreSQL project reports:</p> + <blockquote cite="https://www.postgresql.org/about/news/1949/">; + <p> + An authenticated user could create a stack-based buffer overflow + by changing their own password to a purpose-crafted value. In addition + to the ability to crash the PostgreSQL server, this could be further + exploited to execute arbitrary code as the PostgreSQL operating system account. + </p> + <p> + Additionally, a rogue server could send a specifically crafted + message during the SCRAM authentication process and cause a libpq-enabled client + to either crash or execute arbitrary code as the client's operating system account. + </p> + <p> + This issue is fixed by upgrading and restarting your PostgreSQL + server as well as your libpq installations. All users running + PostgreSQL 10, 11, and 12 beta are encouraged to upgrade as soon as possible. + </p> + </blockquote> + </body> + </description> + <references> + <url>https://www.postgresql.org/about/news/1949/</url>; + <cvename>CVE-2019-10164</cvename> + </references> + <dates> + <discovery>2019-06-20</discovery> + <entry>2019-06-27</entry> + </dates> + </vuln> + <vuln vid="6f15730d-94ea-11e9-a83e-641c67a117d8"> <topic>znc -- privilege escalation</topic> <affects>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201906272105.x5RL5tA2061561>