# CVE-2020-1720: Missing authorization in postgresql > An authenticated attacker can drop database objects like functions and triggers due to missing authorization checks in ALTER DEPENDS ON EXTENSION commands. - **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Mar 2020 - **Updated:** 4 Aug 2024 - **Also known as:** ALPINE-CVE-2020-1720, BIT-postgresql-2020-1720, CLEANSTART-2026-QH42621, DLA-2105-1, DSA-4622-1, DSA-4623-1, GHSA-prcp-93mm-93fm, MGASA-2020-0095, RHBA-2020:2396, SUSE-SU-2020:0586-1, SUSE-SU-2020:0589-1, SUSE-SU-2020:0715-1, SUSE-SU-2020:0752-1, SUSE-SU-2020:2149-1, UBUNTU-CVE-2020-1720, USN-4282-1, openSUSE-SU-2020:0331-1 ## What is CVE-2020-1720? CVE-2020-1720 is a low-severity missing authorization vulnerability in Postgresql Postgresql, published on 17 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A flaw was found in PostgreSQL's "ALTER ... DEPENDS ON EXTENSION", where sub-commands did not perform authorization checks. An authenticated attacker could use this flaw in certain configurations to perform drop objects such as function, triggers, et al., leading to database corruption. This issue affects PostgreSQL versions before 12.2, before 11.7, before 10.12 and before 9.6.17. Weakness: CWE-862 (Missing Authorization), CWE-285 (Improper Authorization) ## Which versions are affected by CVE-2020-1720? 1 open source package ship an affected version, including postgresql. It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `postgresql` | Bitnami | From 9.6.0 | 9.6.17, 10.12.0, 11.7.0, 12.2.0 | | `ovirt-engine` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-backend` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-dbscripts` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-extensions-api-impl` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-extensions-api-impl-javadoc` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-health-check-bundler` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-restapi` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-setup` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-setup-base` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-setup-plugin-cinderlib` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-setup-plugin-ovirt-engine` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-setup-plugin-ovirt-engine-common` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-setup-plugin-vmconsole-proxy-helper` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-setup-plugin-websocket-proxy` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-tools` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-tools-backup` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-vmconsole-proxy-helper` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-webadmin-portal` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `ovirt-engine-websocket-proxy` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `python2-ovirt-engine-lib` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `rh-postgresql10-postgresql` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-contrib` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-contrib-syspaths` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-debuginfo` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-devel` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-docs` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-libs` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-plperl` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-plpython` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-pltcl` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-server` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-server-syspaths` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-static` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-syspaths` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rh-postgresql10-postgresql-test` | Red Hat:rhev_manager:4.3 | All versions | 0:10.12-2.el7 | | `rhvm` | Red Hat:rhev_manager:4.3 | All versions | 0:4.3.10.3-0.2.el7 | | `postgresql10` | SUSE:Enterprise Storage 5 | All versions | 10.12-1.18.1 | | `postgresql10-libs` | SUSE:Enterprise Storage 5 | All versions | 10.12-1.18.1 | | `postgresql96` | SUSE:Enterprise Storage 5 | All versions | 9.6.17-3.33.1 | Products: Postgresql Postgresql, Redhat Decision Manager, Redhat Enterprise Linux, Redhat Software Collections. ## How do I fix CVE-2020-1720? Upgrade postgresql to a fixed version for your release line: 9.6.17, 10.12.0, 11.7.0 or 12.2.0. ## Is CVE-2020-1720 being exploited? There is no known exploitation of CVE-2020-1720 in the wild and no public exploit code. ## Other vulnerabilities in Postgresql Postgresql - [CVE-2013-1902](https://insights.sbomify.com/CVE-2013-1902/): Information disclosure in n/a (critical 10.0) - [CVE-2013-1903](https://insights.sbomify.com/CVE-2013-1903/): Information disclosure in n/a (critical 10.0) - [CVE-2007-3279](https://insights.sbomify.com/CVE-2007-3279/): Privilege escalation in n/a (critical 10.0) - [CVE-2002-1399](https://insights.sbomify.com/CVE-2002-1399/): Integer overflow in n/a (critical 10.0) - [CVE-2016-3065](https://insights.sbomify.com/CVE-2016-3065/): Information disclosure in n/a (critical 9.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-1720 and fix it if it is affected. What it is: CVE-2020-1720 is a low-severity missing authorization vulnerability in Postgresql Postgresql, published on 17 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-1720 in the wild and no public exploit code. Affected packages and fixed versions: - postgresql (Bitnami): affected from 9.6.0; fixed in 9.6.17, 10.12.0, 11.7.0, 12.2.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-1720/ (Markdown: https://insights.sbomify.com/CVE-2020-1720/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-1720 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-1720 - OSV: https://osv.dev/vulnerability/CVE-2020-1720 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-1720/ Summaries are generated and may contain mistakes; the official description above is the record.