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…
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.7% (FIRST EPSS); higher than 89.9% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: postgresql (Alpine:v3.10) 10.1-r0; postgresql14 (Alpine:v3.15) 10.1-r0; postgresql15 (Alpine:v3.17) 10.1-r0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to postgresql (Alpine:v3.10) 10.1-r0; postgresql14 (Alpine:v3.15) 10.1-r0; postgresql15 (Alpine:v3.17) 10.1-r0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 22, 2017
- Updated
- Jun 16, 2026
- EPSS
- 3.7% · 89th percentile
- CWE
- CWE-200
Report tools
Action score
33
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is PostgreSQL on your server exposed to the internet?Run a port scan
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| postgresql | postgresql | cpe:2.3:a:postgresql:postgresql |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Using postgresql? Add it to your stack and be the first to know about CVEs like this one. (PostgreSQL)
Is PostgreSQL on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanVersions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Red Hat, Inc. 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, 9.3.x before 9.3.20affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- postgresql postgresql10
- postgresql postgresql9.3
- postgresql postgresql9.3.1
- postgresql postgresql9.3.10
- postgresql postgresql9.3.11
- postgresql postgresql9.3.12
- postgresql postgresql9.3.13
- postgresql postgresql9.3.14
- postgresql postgresql9.3.15
- postgresql postgresql9.3.16
- postgresql postgresql9.3.17
- postgresql postgresql9.3.18
- postgresql postgresql9.3.19
- postgresql postgresql9.3.2
- postgresql postgresql9.3.3
- postgresql postgresql9.3.4
- postgresql postgresql9.3.5
- postgresql postgresql9.3.6
- postgresql postgresql9.3.7
- postgresql postgresql9.3.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | postgresql | before 10.1-r0 | 10.1-r0 |
| Alpine:v3.15 | postgresql14 | before 10.1-r0 | 10.1-r0 |
| Alpine:v3.17 | postgresql15 | before 10.1-r0 | 10.1-r0 |
| Alpine:v3.3 | postgresql | before 9.4.15-r0 | 9.4.15-r0 |
| Alpine:v3.4 | postgresql | before 9.5.10-r0 | 9.5.10-r0 |
| Alpine:v3.5 | postgresql | before 9.6.6-r0 | 9.6.6-r0 |
| Debian:8 | postgresql-9.4 | before 9.4.15-0+deb8u1 | 9.4.15-0+deb8u1 |
| Debian:9 | postgresql-9.6 | before 9.6.6-0+deb9u1 | 9.6.6-0+deb9u1 |
| openSUSE:Tumbleweed | postgresql10 | before 10.18-1.3 | 10.18-1.3 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql95-postgresql | before 0:9.5.14-1.el6 | 0:9.5.14-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql95-postgresql-contrib | before 0:9.5.14-1.el6 | 0:9.5.14-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql95-postgresql-debuginfo | before 0:9.5.14-1.el6 | 0:9.5.14-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql95-postgresql-devel | before 0:9.5.14-1.el6 | 0:9.5.14-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql95-postgresql-docs | before 0:9.5.14-1.el6 | 0:9.5.14-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql95-postgresql-libs | before 0:9.5.14-1.el6 | 0:9.5.14-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql95-postgresql-plperl | before 0:9.5.14-1.el6 | 0:9.5.14-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql95-postgresql-plpython | before 0:9.5.14-1.el6 | 0:9.5.14-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql95-postgresql-pltcl | before 0:9.5.14-1.el6 | 0:9.5.14-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql95-postgresql-server | before 0:9.5.14-1.el6 | 0:9.5.14-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql95-postgresql-static | before 0:9.5.14-1.el6 | 0:9.5.14-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql95-postgresql-test | before 0:9.5.14-1.el6 | 0:9.5.14-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-contrib | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-contrib-syspaths | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
+45
Same product
postgresql: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-7546PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allowing remote…57Plan
- CVE-2019-9193In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' group to…55Plan
- CVE-2020-25695A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24.49Plan
Published before and after this one in the same product
- ← EarlierCVE-2017-7548Aug 16, 2017 · PostgreSQL versions before 9.4.13, 9.5.8 and 9.6.4 are vulnerable to authorization flaw allowing remote authenticated attackers with no…31Monitor
- ← EarlierCVE-2017-8806Nov 13, 2017 · The Debian pg_ctlcluster, pg_createcluster, and pg_upgradecluster scripts, as distributed in the Debian postgresql-common package before…22Monitor
- Later →CVE-2017-15099Nov 22, 2017 · INSERT ...28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:postgresql | 10.1-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:postgresql14 | 10.1-r0 · Alpine:v3.15 | Package registry (OSV) |
| alpine:postgresql15 | 10.1-r0 · Alpine:v3.17 | Package registry (OSV) |
| debian:postgresql-9.4 | 9.4.15-0+deb8u1 · Debian:8 | Package registry (OSV) |
| debian:postgresql-9.6 | 9.6.6-0+deb9u1 · Debian:9 | Package registry (OSV) |
| opensuse:postgresql10 | 10.18-1.3 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql | 0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-contrib | 0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-debuginfo | 0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-devel | 0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-docs | 0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-libs | 0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-plperl | 0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-plpython | 0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-pltcl | 0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-server | 0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-static | 0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-test | 0:9.5.14-1.el6 · Red Hat:rhel_software_collections:3::el6 | Package registry (OSV) |
| suse:postgresql94 | 9.4.15-0.23.10.1 · SUSE:Linux Enterprise Server 11 SP4 | Package registry (OSV) |
| suse:postgresql94-libs | 9.4.15-0.23.10.1 · SUSE:Linux Enterprise Software Development Kit 11 SP4 | Package registry (OSV) |
| suse:postgresql96 | 9.6.6-3.10.1 · SUSE:Linux Enterprise Desktop 12 SP2 | Package registry (OSV) |
| suse:postgresql96-libs | 9.6.6-3.10.1 · SUSE:Linux Enterprise Desktop 12 SP2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-094 · Feb 18, 2020(Postgresql Sunucu Güvenlik Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-200 · Exposure of Sensitive Information to an Unauthorized ActorCVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Root cause
The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.
The bug in code
The whole CWE-200 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
{
"permissions": ["tabs", "<all_urls>"],
"background": { "service_worker": "analytics.js" }
}Fixed
{
"permissions": ["activeTab"],
"host_permissions": ["https://yildiz.example/*"]
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- ExcavationCAPEC-116likelihood: High · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- FootprintingCAPEC-169likelihood: High · Very Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- FingerprintingCAPEC-224likelihood: High · Very Low
- ICMP Echo Request PingCAPEC-285likelihood: Medium · Low
- TCP SYN ScanCAPEC-287Low
- Enumerate Mail Exchange (MX) RecordsCAPEC-290Low
ATT&CK techniques
- System Service DiscoveryT1007
- System Network Configuration DiscoveryT1016
- Remote System DiscoveryT1018
- System Owner/User DiscoveryT1033
- Masquerading: Match Legitimate Name or LocationT1036.005
- Network Service ScanningT1046
- System Network Connections DiscoveryT1049
- Process DiscoveryT1057
- Permission Groups DiscoveryT1069
- System Information DiscoveryT1082
- File and Directory DiscoveryT1083
- Account DiscoveryT1087
- Multi-Factor Authentication InterceptionT1111
- Peripheral Device DiscoveryT1120
- System Time DiscoveryT1124
- Access Token Manipulation:Token Impersonation/TheftT1134.001
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.