CVE-2017-15098
UnknownEPSS 3.72%
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?
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.
How severe is CVE-2017-15098?
Severity scoring for CVE-2017-15098 is pending analysis. The EPSS model estimates a 3.72% probability of exploitation in the next 30 days.
How do I fix CVE-2017-15098?
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 2017
- CVE-2017-15092A cross-site scripting issue has been found in the web inter…
- CVE-2017-15093When api-config-dir is set to a non-empty value, which is no…
- CVE-2017-15094An issue has been found in the DNSSEC parsing code of PowerD…
- CVE-2017-15095A deserialization flaw was discovered in the jackson-databin…9.8
- CVE-2017-15096A flaw was found in GlusterFS in versions prior to 3.10. A n…
- CVE-2017-15097Privilege escalation flaws were found in the Red Hat initial…6.5
- CVE-2017-15099INSERT ... ON CONFLICT DO UPDATE commands in PostgreSQL 10.x…
- CVE-2017-15100An attacker submitting facts to the Foreman server containin…6.1
- CVE-2017-15101A missing patch for a stack-based buffer overflow in findTab…7.8
- CVE-2017-15102The tower_probe function in drivers/usb/misc/legousbtower.c …
- CVE-2017-15103A security-check flaw was found in the way the Heketi 5 serv…
- CVE-2017-15104An access flaw was found in Heketi 5, where the heketi.json …7.8
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