CVE-2020-14349: It was found that PostgreSQL versions before 12.4, before 11.9 and before 10.14 did not properly sanitize the search_path during logical replication.
High CVSS 7.1
- CVE id
- CVE-2020-14349
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| PostgreSQL Runtimes and servers |
>= 10.0, < 10.14 >= 11.0, < 11.9 >= 12.0, < 12.4 |
10.14, 11.9, 12.4 |
How to fix it
Upgrade PostgreSQL to the fixed release of the line you run: 10.14, 11.9, 12.4.
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
It was found that PostgreSQL versions before 12.4, before 11.9 and before 10.14 did not properly sanitize the search_path during logical replication. An authenticated attacker could use this flaw in an attack similar to CVE-2018-1058, in order to execute arbitrary SQL command in the context of the user used for replication.
References
- CVE-2020-14349 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2020-14349
- Web: https://bugzilla.redhat.com/show_bug.cgi?id=1865744
- Web: https://security.gentoo.org/glsa/202008-13
- Web: https://security.netapp.com/advisory/ntap-20200918-0002/
- Web: https://usn.ubuntu.com/4472-1/
- Web: https://bugzilla.redhat.com/show_bug.cgi?id=1865744
- Web: https://security.gentoo.org/glsa/202008-13
- Web: https://security.netapp.com/advisory/ntap-20200918-0002/
- Web: https://usn.ubuntu.com/4472-1/
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.