CVE-2019-10129: A vulnerability was found in postgresql versions 11.x prior to 11.3.
Medium CVSS 6.5
- CVE id
- CVE-2019-10129
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| PostgreSQL Runtimes and servers |
>= 11.0, < 11.3 | 11.3 |
How to fix it
Upgrade PostgreSQL to 11.3 or later.
psql -c 'SELECT version();'
- Install the patched PostgreSQL minor release of your major version (the postgres image tag, the PGDG packages, or your provider's maintenance update) and restart the server; minor releases need no dump or pg_upgrade.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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).
References
- CVE-2019-10129 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2019-10129
- Web: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10129
- Web: https://security.gentoo.org/glsa/202003-03
- Web: https://www.postgresql.org/about/news/1939/
- Web: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10129
- Web: https://security.gentoo.org/glsa/202003-03
- Web: https://www.postgresql.org/about/news/1939/
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.