CVE-2020-14350: It was found that some PostgreSQL extensions did not use search_path safely in their installation script.

High CVSS 7.3

CVE id
CVE-2020-14350
Published
Last modified

Affected packages

PackageAffected versionsFixed in
PostgreSQL
Runtimes and servers
>= 9.5, < 9.5.23
>= 9.6, < 9.6.19
>= 10.0, < 10.14
>= 11.0, < 11.9
>= 12.0, < 12.4
9.5.23, 9.6.19, 10.14, 11.9, 12.4

How to fix it

Upgrade PostgreSQL to the fixed release of the line you run: 9.5.23, 9.6.19, 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 some PostgreSQL extensions did not use search_path safely in their installation script. An attacker with sufficient privileges could use this flaw to trick an administrator into executing a specially crafted script, during the installation or update of such extension. This affects PostgreSQL versions before 12.4, before 11.9, before 10.14, before 9.6.19, and before 9.5.23.

References

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.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

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.