LiveActive security incident?Get immediate response
CVE Record

CVE-2017-15098: Invalid json_populate_recordset or jsonb_populate_recordset function calls in PostgreSQL 10.x before 10.1,...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-15098 affects older PostgreSQL releases. Certain malformed calls to JSON recordset functions could crash the database server or leak a few bytes of server memory. For executives, the main risk is service disruption to dependent applications, with limited information disclosure also possible.

Executive priority

Treat this as a patch and inventory item, not an emergency based on the provided evidence. Prioritize if affected PostgreSQL supports critical services, has broad user access, or has experienced unexplained database crashes.

Technical view

The issue involves 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. The source maps it to CWE-200.

Likely exposure

Exposure is most likely where affected PostgreSQL versions remain deployed and database users or application paths can cause these JSON functions to be invoked. Internet exposure depends on application and database access controls, which are not described in the sources.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. Public references confirm vendor advisories and fixed releases, but no exploit status is provided here.

Researcher notes

No CVSS score is included in the bundle. The confirmed impact is crash or small memory disclosure through invalid JSON populate recordset calls. Avoid assuming unauthenticated exploitation unless separate evidence shows SQL execution is reachable.

Mitigation direction

  • Upgrade PostgreSQL to 10.1, 9.6.6, 9.5.10, 9.4.15, or 9.3.20 or later.
  • Apply relevant Debian or Red Hat security updates where PostgreSQL is vendor-packaged.
  • Check PostgreSQL vendor security guidance for supported upgrade paths.
  • Prioritize systems hosting critical applications or untrusted database clients.

Validation and detection

  • Inventory PostgreSQL versions across production, staging, and managed database environments.
  • Confirm installed package versions match fixed releases or vendor advisory updates.
  • Review whether applications expose database functionality to untrusted users.
  • Check database logs for unexpected server crashes around JSON recordset function use.
Prepared
Confidence
high
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-15098 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red Hat, Inc.postgresql10.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.20Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.