CVE-2017-15098: Infoleak
First published: Thu Nov 02 2017(Updated: )
Invalid json_populate_recordset or jsonb_populate_recordset function calls in PostgreSQL 10.x before 10.1, 9.6.x before 9.6.6, 9.5.x before 9.5.10, 9.4.x before 9.4.15, and 9.3.x before 9.3.20 can crash the server or disclose a few bytes of server memory.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/postgresql-10 | ||
| debian/postgresql-9.1 | ||
| redhat/postgresql | <9.3.20 | 9.3.20 |
| redhat/postgresql | <9.4.15 | 9.4.15 |
| redhat/postgresql | <9.5.10 | 9.5.10 |
| redhat/postgresql | <9.6.6 | 9.6.6 |
| redhat/postgresql | <10.1 | 10.1 |
| PostgreSQL | =9.3 | |
| PostgreSQL | =9.3.1 | |
| PostgreSQL | =9.3.2 | |
| PostgreSQL | =9.3.3 | |
| PostgreSQL | =9.3.4 | |
| PostgreSQL | =9.3.5 | |
| PostgreSQL | =9.3.6 | |
| PostgreSQL | =9.3.7 | |
| PostgreSQL | =9.3.8 | |
| PostgreSQL | =9.3.9 | |
| PostgreSQL | =9.3.10 | |
| PostgreSQL | =9.3.11 | |
| PostgreSQL | =9.3.12 | |
| PostgreSQL | =9.3.13 | |
| PostgreSQL | =9.3.14 | |
| PostgreSQL | =9.3.15 | |
| PostgreSQL | =9.3.16 | |
| PostgreSQL | =9.3.17 | |
| PostgreSQL | =9.3.18 | |
| PostgreSQL | =9.3.19 | |
| PostgreSQL | =9.4 | |
| PostgreSQL | =9.4.1 | |
| PostgreSQL | =9.4.2 | |
| PostgreSQL | =9.4.3 | |
| PostgreSQL | =9.4.4 | |
| PostgreSQL | =9.4.5 | |
| PostgreSQL | =9.4.6 | |
| PostgreSQL | =9.4.7 | |
| PostgreSQL | =9.4.8 | |
| PostgreSQL | =9.4.9 | |
| PostgreSQL | =9.4.10 | |
| PostgreSQL | =9.4.11 | |
| PostgreSQL | =9.4.12 | |
| PostgreSQL | =9.4.13 | |
| PostgreSQL | =9.4.14 | |
| PostgreSQL | =9.5 | |
| PostgreSQL | =9.5.1 | |
| PostgreSQL | =9.5.2 | |
| PostgreSQL | =9.5.3 | |
| PostgreSQL | =9.5.4 | |
| PostgreSQL | =9.5.5 | |
| PostgreSQL | =9.5.6 | |
| PostgreSQL | =9.5.7 | |
| PostgreSQL | =9.5.8 | |
| PostgreSQL | =9.5.9 | |
| PostgreSQL | =9.6 | |
| PostgreSQL | =9.6.1 | |
| PostgreSQL | =9.6.2 | |
| PostgreSQL | =9.6.3 | |
| PostgreSQL | =9.6.4 | |
| PostgreSQL | =9.6.5 | |
| PostgreSQL | =10 | |
| Debian | =8.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.securityfocus.com/bid/101781
- http://www.securitytracker.com/id/1039752
- https://access.redhat.com/errata/RHSA-2018:2511
- https://access.redhat.com/errata/RHSA-2018:2566
- https://www.debian.org/security/2017/dsa-4027
- https://www.debian.org/security/2017/dsa-4028
- https://www.postgresql.org/about/news/1801/
- https://www.postgresql.org/support/security/
- https://access.redhat.com/security/updates/classification/
- https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=37a795a60
- https://bugzilla.redhat.com/show_bug.cgi?id=1508820
- https://security-tracker.debian.org/tracker/CVE-2017-15098
Frequently Asked Questions
What is the severity of CVE-2017-15098?
CVE-2017-15098 is classified as a medium severity vulnerability that can cause server crashes or reveal sensitive memory contents in PostgreSQL.
How do I fix CVE-2017-15098?
To resolve CVE-2017-15098, upgrade PostgreSQL to version 10.1, 9.6.6, 9.5.10, 9.4.15, or 9.3.20 or later.
What outcomes can occur if CVE-2017-15098 is exploited?
Exploitation of CVE-2017-15098 may lead to a server crash or potential exposure of sensitive information from memory.
Which PostgreSQL versions are affected by CVE-2017-15098?
CVE-2017-15098 affects PostgreSQL versions 10.x before 10.1, 9.6.x before 9.6.6, 9.5.x before 9.5.10, 9.4.x before 9.4.15, and 9.3.x before 9.3.20.
Is there a workaround for CVE-2017-15098?
While upgrading is the recommended solution for CVE-2017-15098, users can mitigate risks by avoiding the use of invalid json_populate_recordset or jsonb_populate_recordset function calls.
- collector/security-tracker-debian
- agent/type
- agent/first-publish-date
- agent/severity
- agent/weakness
- agent/author
- agent/references
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2017-15098
- agent/software-canonical-lookup
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- package-manager/debian
- package-manager/redhat
- vendor/postgresql
- canonical/postgresql
- version/postgresql/9.3
- version/postgresql/9.3.1
- version/postgresql/9.3.2
- version/postgresql/9.3.3
- version/postgresql/9.3.4
- version/postgresql/9.3.5
- version/postgresql/9.3.6
- version/postgresql/9.3.7
- version/postgresql/9.3.8
- version/postgresql/9.3.9
- version/postgresql/9.3.10
- version/postgresql/9.3.11
- version/postgresql/9.3.12
- version/postgresql/9.3.13
- version/postgresql/9.3.14
- version/postgresql/9.3.15
- version/postgresql/9.3.16
- version/postgresql/9.3.17
- version/postgresql/9.3.18
- version/postgresql/9.3.19
- version/postgresql/9.4
- version/postgresql/9.4.1
- version/postgresql/9.4.2
- version/postgresql/9.4.3
- version/postgresql/9.4.4
- version/postgresql/9.4.5
- version/postgresql/9.4.6
- version/postgresql/9.4.7
- version/postgresql/9.4.8
- version/postgresql/9.4.9
- version/postgresql/9.4.10
- version/postgresql/9.4.11
- version/postgresql/9.4.12
- version/postgresql/9.4.13
- version/postgresql/9.4.14
- version/postgresql/9.5
- version/postgresql/9.5.1
- version/postgresql/9.5.2
- version/postgresql/9.5.3
- version/postgresql/9.5.4
- version/postgresql/9.5.5
- version/postgresql/9.5.6
- version/postgresql/9.5.7
- version/postgresql/9.5.8
- version/postgresql/9.5.9
- version/postgresql/9.6
- version/postgresql/9.6.1
- version/postgresql/9.6.2
- version/postgresql/9.6.3
- version/postgresql/9.6.4
- version/postgresql/9.6.5
- version/postgresql/10
- vendor/debian
- canonical/debian
- version/debian/8.0