CVE-2017-15098
Last modified
CVE-2017-15098 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 3.72% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| 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.3.14 |
| Postgresql | Postgresql | 9.3.15 |
| Postgresql | Postgresql | 9.3.16 |
| Postgresql | Postgresql | 9.3.17 |
| Postgresql | Postgresql | 9.3.18 |
| Postgresql | Postgresql | 9.3.19 |
| 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.4.9 |
| Postgresql | Postgresql | 9.4.10 |
| Postgresql | Postgresql | 9.4.11 |
| Postgresql | Postgresql | 9.4.12 |
| Postgresql | Postgresql | 9.4.13 |
| Postgresql | Postgresql | 9.4.14 |
| Postgresql | Postgresql | 9.5 |
| Postgresql | Postgresql | 9.5.1 |
| Postgresql | Postgresql | 9.5.2 |
| Postgresql | Postgresql | 9.5.3 |
| Postgresql | Postgresql | 9.5.4 |
| Postgresql | Postgresql | 9.5.5 |
| Postgresql | Postgresql | 9.5.6 |
| Postgresql | Postgresql | 9.5.7 |
| Postgresql | Postgresql | 9.5.8 |
| Postgresql | Postgresql | 9.5.9 |
| Postgresql | Postgresql | 9.6 |
| Postgresql | Postgresql | 9.6.1 |
| Postgresql | Postgresql | 9.6.2 |
| Postgresql | Postgresql | 9.6.3 |
| Postgresql | Postgresql | 9.6.4 |
Showing 50 of 53 affected configurations. See NVD for the full list.
References
- http://www.securityfocus.com/bid/101781Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1039752Third Party Advisory, VDB Entry
- https://www.debian.org/security/2017/dsa-4027Issue Tracking, Third Party Advisory
- https://www.debian.org/security/2017/dsa-4028Issue Tracking, Third Party Advisory
- https://www.postgresql.org/about/news/1801/Issue Tracking, Vendor Advisory
- https://www.postgresql.org/support/security/Issue Tracking, Vendor Advisory
- http://www.securityfocus.com/bid/101781Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1039752Third Party Advisory, VDB Entry
- https://www.debian.org/security/2017/dsa-4027Issue Tracking, Third Party Advisory
- https://www.debian.org/security/2017/dsa-4028Issue Tracking, Third Party Advisory
- https://www.postgresql.org/about/news/1801/Issue Tracking, Vendor Advisory
- https://www.postgresql.org/support/security/Issue Tracking, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-15098?
How severe is CVE-2017-15098?
How do I fix CVE-2017-15098?
Are you affected by CVE-2017-15098?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST