CVE-2016-5423
UnknownEPSS 6.01%
Last modified
CVE-2016-5423 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 6.01% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| 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 |
References
- http://www.debian.org/security/2016/dsa-3646Third Party Advisory
- http://www.securityfocus.com/bid/92433Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1036617Third Party Advisory, VDB Entry
- https://bugzilla.redhat.com/show_bug.cgi?id=1364001Issue Tracking, Third Party Advisory, VDB Entry
- https://www.postgresql.org/about/news/1688/Patch, Vendor Advisory
- https://www.postgresql.org/docs/current/static/release-9-1-23.htmlRelease Notes, Vendor Advisory
- https://www.postgresql.org/docs/current/static/release-9-2-18.htmlRelease Notes, Vendor Advisory
- https://www.postgresql.org/docs/current/static/release-9-3-14.htmlRelease Notes, Vendor Advisory
- https://www.postgresql.org/docs/current/static/release-9-4-9.htmlRelease Notes, Vendor Advisory
- https://www.postgresql.org/docs/current/static/release-9-5-4.htmlRelease Notes, Vendor Advisory
- http://www.debian.org/security/2016/dsa-3646Third Party Advisory
- http://www.securityfocus.com/bid/92433Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1036617Third Party Advisory, VDB Entry
- https://bugzilla.redhat.com/show_bug.cgi?id=1364001Issue Tracking, Third Party Advisory, VDB Entry
- https://www.postgresql.org/about/news/1688/Patch, Vendor Advisory
- https://www.postgresql.org/docs/current/static/release-9-1-23.htmlRelease Notes, Vendor Advisory
- https://www.postgresql.org/docs/current/static/release-9-2-18.htmlRelease Notes, Vendor Advisory
- https://www.postgresql.org/docs/current/static/release-9-3-14.htmlRelease Notes, Vendor Advisory
- https://www.postgresql.org/docs/current/static/release-9-4-9.htmlRelease Notes, Vendor Advisory
- https://www.postgresql.org/docs/current/static/release-9-5-4.htmlRelease Notes, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is 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.
How severe is CVE-2016-5423?
Severity scoring for CVE-2016-5423 is pending analysis. The EPSS model estimates a 6.01% probability of exploitation in the next 30 days.
How do I fix CVE-2016-5423?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-5417Memory leak in the __res_vinit function in the IPv6 name ser…
- CVE-2016-5418The sandboxing code in libarchive 3.2.0 and earlier mishandl…
- CVE-2016-5419curl and libcurl before 7.50.1 do not prevent TLS session re…
- CVE-2016-5420curl and libcurl before 7.50.1 do not check the client certi…
- CVE-2016-5421Use-after-free vulnerability in libcurl before 7.50.1 allows…8.1
- CVE-2016-5422The web console in Red Hat JBoss Operations Network (JON) be…
- CVE-2016-5424PostgreSQL before 9.1.23, 9.2.x before 9.2.18, 9.3.x before …
- CVE-2016-5425The Tomcat package on Red Hat Enterprise Linux (RHEL) 7, Fed…7.8
- CVE-2016-5426PowerDNS (aka pdns) Authoritative Server before 3.4.10 allow…
- CVE-2016-5427PowerDNS (aka pdns) Authoritative Server before 3.4.10 does …
- CVE-2016-5428Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2016-5429jose-php before 2.2.1 does not use constant-time operations …3.7
Are you affected by CVE-2016-5423?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST