LiveActive security incident?Get immediate response
CVE Record

CVE-2019-10129: A vulnerability was found in postgresql versions 11.x prior to 11.3.

A vulnerability was found in postgresql versions 11.x prior to 11.3. Using a purpose-crafted insert to a partitioned table, an attacker can read arbitrary bytes of server memory. In the default configuration, any user can create a partitioned table suitable for this attack. (Exploit prerequisites are the same as for CVE-2018-1052).

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-10129 is an information disclosure flaw in PostgreSQL 11 before 11.3. A logged-in database user could use a crafted insert into a partitioned table to read arbitrary bytes from server memory. The main business risk is exposure of sensitive data held in database server memory.

Executive priority

Treat this as a moderate-priority confidentiality issue. It is not described as remotely exploitable without credentials, but it can expose sensitive server memory where low-privileged database access exists. Patch affected PostgreSQL 11 systems during the next controlled maintenance window, sooner for shared or externally reachable databases.

Technical view

The issue is a CWE-125 out-of-bounds read in PostgreSQL 11.x prior to 11.3. It is network-reachable with low privileges and no user interaction. The CVSS 3.0 score is 6.5, driven by high confidentiality impact with no stated integrity or availability impact.

Likely exposure

Exposure is limited to PostgreSQL 11.x deployments before 11.3 where untrusted or low-privileged users can connect and create suitable partitioned tables. The source states the default configuration allows any user to create such a table.

Exploitation context

The bundle does not cite active exploitation, and the CVE is not marked as CISA KEV. Exploitation requires an authenticated database user and a purpose-crafted insert into a partitioned table. No public source in the bundle provides safe validation payloads or exploit prevalence.

Researcher notes

Key boundaries are clear: PostgreSQL 11.x before 11.3, authenticated low-privilege access, crafted insert, partitioned table, arbitrary server-memory read. The bundle does not establish affected versions outside PostgreSQL 11.x, active exploitation, or mitigations beyond moving to fixed vendor releases.

Mitigation direction

  • Upgrade PostgreSQL 11.x instances to 11.3 or a later supported vendor-fixed release.
  • Apply distribution vendor updates, including Gentoo or Red Hat packages where applicable.
  • Identify untrusted database users and review table-creation privileges against vendor guidance.
  • Prioritize internet-accessible or multi-tenant database environments first.

Validation and detection

  • Inventory PostgreSQL versions and flag 11.x releases earlier than 11.3.
  • Confirm vendor package advisories show the installed build includes the fix.
  • Review database roles that can connect and create partitioned tables.
  • Check logs and monitoring for unexpected partitioned table creation by low-privileged users.
Prepared
Confidence
high
Sources
5

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 · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-2019-10129 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
Medium
CVSS
6.5 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

6.5Medium
CVSS 3.0 vector shape for CVE-2019-10129Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PostgreSQL Projectpostgresql11.x prior to 11.3Listed
Weakness

CWE details

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

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.