CVE-2016-5423

PostgreSQL before 9.1.23, 9.2.x before 9.2.18, 9.3.x before 9.3.14, 9.4.x before 9.4.9, and 9.5.x before 9.5.4 allow remote authenticated users to cause a denial of service (NULL pointer dereference and server crash), obtain sensitive memory information, or possibly execute arbitrary code via (1) a CASE expression within the test value subexpression of another CASE or (2) inlining of an SQL function that implements the equality operator used for a CASE expression involving values of different types.

It was discovered that certain SQL statements containing CASE/WHEN commands could crash the PostgreSQL server, or disclose a few bytes of server memory, potentially leading to arbitrary code execution (CVE-2016-5423).

It was found that PostgreSQL client programs mishandle database and role names containing newlines, carriage returns, double quotes, or backslashes. By crafting such an object name, roles with the CREATEDB or CREATEROLE option could escalate their privileges to root when a root user next executes maintenance with a vulnerable program. Vulnerable programs include pg_dumpall, pg_upgrade, vacuumdb, reindexdb, and clusterdb (CVE-2016-5424).

These are all security issues fixed in the postgresql94-9.4.10-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the postgresql93-9.3.15-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the libecpg6-32bit-9.5.4-1.2 package on the GA media of openSUSE Tumbleweed.

This update for postgresql93 to version 9.3.14 fixes the several issues.

These security issues were fixed:

• CVE-2016-5423: CASE/WHEN with inlining can cause untrusted pointer dereference (bsc#993454).
• CVE-2016-5424: Fix client programs' handling of special characters in database and role names (bsc#993453).

This non-security issue was fixed:

• bsc#973660: Added 'Requires: timezone' to Service Pack

For additional non-security issues please refer to

• http://www.postgresql.org/docs/9.3/static/release-9-3-14.html
• http://www.postgresql.org/docs/9.3/static/release-9-3-13.html
• http://www.postgresql.org/docs/9.4/static/release-9-3-12.html

This update for postgresql94 to version 9.4.9 fixes the several issues.

These security issues were fixed:

• CVE-2016-5423: CASE/WHEN with inlining can cause untrusted pointer dereference (bsc#993454).
• CVE-2016-5424: Fix client programs' handling of special characters in database and role names (bsc#993453).

This non-security issue was fixed:

• bsc#973660: Added 'Requires: timezone' to Service Pack

For additional non-security issues please refer to

• http://www.postgresql.org/docs/9.4/static/release-9-4-9.html
• http://www.postgresql.org/docs/9.4/static/release-9-4-8.html
• http://www.postgresql.org/docs/9.4/static/release-9-4-7.html

This update for postgresql94 to version 9.4.9 fixes the several issues.

These security issues were fixed:

• CVE-2016-5423: CASE/WHEN with inlining can cause untrusted pointer dereference (bsc#993454).
• CVE-2016-5424: Fix client programs' handling of special characters in database and role names (bsc#993453).

For the non-security issues please refer to

• http://www.postgresql.org/docs/9.4/static/release-9-4-9.html
• http://www.postgresql.org/docs/9.4/static/release-9-4-8.html
• http://www.postgresql.org/docs/9.4/static/release-9-4-7.html

Heikki Linnakangas discovered that PostgreSQL incorrectly handled certain nested CASE/WHEN expressions. A remote attacker could possibly use this issue to cause PostgreSQL to crash, resulting in a denial of service. (CVE-2016-5423)

Nathan Bossart discovered that PostgreSQL incorrectly handled special characters in database and role names. A remote attacker could possibly use this issue to escalate privileges. (CVE-2016-5424)