CVE-2016-5423: Null Pointer Dereference

Published Aug 4, 2016
·
Updated

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.

Other sources

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.

MITRE

Affected Software

52 affected componentsFixes available
redhat/postgresql<9.5.4
9.5.4
redhat/postgresql<9.4.9
9.4.9
redhat/postgresql<9.3.14
9.3.14
redhat/postgresql<9.2.18
9.2.18
redhat/postgresql<9.1.23
9.1.23
Debian Debian Linux=8.0
PostgreSQL postgresql<=9.1.22
PostgreSQL postgresql=9.2
PostgreSQL postgresql=9.2.1
PostgreSQL postgresql=9.2.2
PostgreSQL postgresql=9.2.3
PostgreSQL postgresql=9.2.4
PostgreSQL postgresql=9.2.5
PostgreSQL postgresql=9.2.6
PostgreSQL postgresql=9.2.7
PostgreSQL postgresql=9.2.8
PostgreSQL postgresql=9.2.9
PostgreSQL postgresql=9.2.10
PostgreSQL postgresql=9.2.11
PostgreSQL postgresql=9.2.12
PostgreSQL postgresql=9.2.13
PostgreSQL postgresql=9.2.14
PostgreSQL postgresql=9.2.15
PostgreSQL postgresql=9.2.16
PostgreSQL postgresql=9.2.17
PostgreSQL postgresql=9.3
PostgreSQL postgresql=9.3.1
PostgreSQL postgresql=9.3.2
PostgreSQL postgresql=9.3.3
PostgreSQL postgresql=9.3.4
PostgreSQL postgresql=9.3.5
PostgreSQL postgresql=9.3.6
PostgreSQL postgresql=9.3.7
PostgreSQL postgresql=9.3.8
PostgreSQL postgresql=9.3.9
PostgreSQL postgresql=9.3.10
PostgreSQL postgresql=9.3.11
PostgreSQL postgresql=9.3.12
PostgreSQL postgresql=9.3.13
PostgreSQL postgresql=9.4
PostgreSQL postgresql=9.4.1
PostgreSQL postgresql=9.4.2
PostgreSQL postgresql=9.4.3
PostgreSQL postgresql=9.4.4
PostgreSQL postgresql=9.4.5
PostgreSQL postgresql=9.4.6
PostgreSQL postgresql=9.4.7
PostgreSQL postgresql=9.4.8
PostgreSQL postgresql=9.5
PostgreSQL postgresql=9.5.1
PostgreSQL postgresql=9.5.2
PostgreSQL postgresql=9.5.3

Event History

Dec 9, 2016
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2016-5423?

CVE-2016-5423 is classified as a high severity vulnerability due to potential remote code execution and denial of service.

2

How do I fix CVE-2016-5423?

To fix CVE-2016-5423, upgrade your PostgreSQL installation to version 9.1.23, 9.2.18, 9.3.14, 9.4.9, or 9.5.4 or later.

3

What versions of PostgreSQL are affected by CVE-2016-5423?

CVE-2016-5423 affects PostgreSQL versions prior to 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.

4

What can attackers do with CVE-2016-5423?

Attackers can exploit CVE-2016-5423 to cause a denial of service, access sensitive memory information, or potentially execute arbitrary code.

5

Who is affected by CVE-2016-5423?

Remote authenticated users of the affected PostgreSQL versions are primarily at risk of CVE-2016-5423.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203