CVE-2017-15098
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data exposure, service disruption.
- Exploit odds
- 3.7% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 3.7% in the next 30 days (EPSS).
- Severity: 8.1 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 3.7% · EPSS, next 30 days
- Weakness
- CWE-200 · Information exposure
- Record status
- Modified
Affected
- 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
Attack profile CVSS 3.0 · 8.1
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-15098.md and follow it. Check whether this project is affected by CVE-2017-15098. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://www.postgresql.org/about/news/1801/
- https://www.postgresql.org/support/security/
- https://www.postgresql.org/about/news/1801/
- https://www.postgresql.org/support/security/
References
- 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/
- 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/