CVE-2019-10129
First published: Tue Jul 30 2019(Updated: )
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).
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| PostgreSQL PostgreSQL | >=11.0<11.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2019-10129?
CVE-2019-10129 is a vulnerability found in PostgreSQL versions 11.x prior to 11.3 that allows an attacker to read arbitrary bytes of server memory.
What is the severity of CVE-2019-10129?
The severity of CVE-2019-10129 is medium, with a CVSS score of 6.5.
How can an attacker exploit CVE-2019-10129?
An attacker can exploit CVE-2019-10129 by using a purpose-crafted insert to a partitioned table, allowing them to read arbitrary bytes of server memory.
Which versions of PostgreSQL are affected by CVE-2019-10129?
PostgreSQL versions 11.x prior to 11.3 are affected by CVE-2019-10129.
Is there a fix for CVE-2019-10129?
Yes, upgrading to PostgreSQL version 11.3 or later will address the vulnerability.
- agent/weakness
- agent/references
- agent/severity
- agent/author
- agent/tags
- agent/event
- agent/type
- agent/description
- agent/last-modified-date
- agent/first-publish-date
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/postgresql
- canonical/postgresql postgresql
- version/postgresql postgresql/11.0