Add info about security vulnerability in PostgreSQL

Security:	CVE-2018-16850
This commit is contained in:
Palle Girgensohn 2018-11-08 23:08:55 +00:00
parent ef51b0bebe
commit 4c4f74caff
Notes: svn2git 2021-03-31 03:12:20 +00:00
svn path=/head/; revision=484486

View file

@ -58,6 +58,56 @@ Notes:
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.)
-->
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
<vuln vid="1c27a706-e3aa-11e8-b77a-6cc21735f730">
<topic>PostgreSQL -- SQL injection in pg_upgrade and pg_dump</topic>
<affects>
<package>
<name>postgresql10-server</name>
<range><lt>10.6</lt></range>
</package>
<package>
<name>postgresql96-server</name>
<range><lt>9.6.11</lt></range>
</package>
<package>
<name>postgresql95-server</name>
<range><lt>9.5.15</lt></range>
</package>
<package>
<name>postgresql94-server</name>
<range><lt>9.4.20</lt></range>
</package>
<package>
<name>postgresql93-server</name>
<range><lt>9.3.25</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/1878/">
<p>CVE-2018-16850: SQL injection in pg_upgrade and pg_dump,
via CREATE TRIGGER ... REFERENCING.</p>
<p>Using a purpose-crafted trigger definition, an attacker can run
arbitrary SQL statements with superuser privileges when a superuser
runs pg_upgrade on the database or during a pg_dump dump/restore
cycle. This attack requires a CREATE privilege on some non-temporary
schema or a TRIGGER privilege on a table. This is exploitable in the
default PostgreSQL configuration, where all users have CREATE
privilege on public schema.</p>
</blockquote>
</body>
</description>
<references>
<url>https://www.postgresql.org/about/news/1905/</url>
<cvename>CVE-2018-16850</cvename>
</references>
<dates>
<discovery>2018-11-08</discovery>
<entry>2018-11-08</entry>
</dates>
</vuln>
<vuln vid="84ca56be-e1de-11e8-bcfd-00e04c1ea73d">
<topic>NGINX -- Multiple vulnerabilities</topic>
<affects>