8.1
CWE
862 285
Advisory Published
CVE Published
CVE Published
Updated

CVE-2020-1720

First published: Thu Feb 06 2020(Updated: )

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.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/rh-postgresql10-postgresql<0:10.12-2.el7
0:10.12-2.el7
redhat/rh-postgresql96-postgresql<0:9.6.19-1.el7
0:9.6.19-1.el7
redhat/rh-postgresql12-postgresql<0:12.4-1.el7
0:12.4-1.el7
IBM Data Risk Manager<=2.0.6
redhat/PostgreSQL<12.2
12.2
redhat/PostgreSQL<11.7
11.7
redhat/PostgreSQL<10.12
10.12
redhat/PostgreSQL<9.6.17
9.6.17
PostgreSQL PostgreSQL>=9.6<9.6.17
PostgreSQL PostgreSQL>=10.0<10.12
PostgreSQL PostgreSQL>=11.0<11.7
PostgreSQL PostgreSQL>=12.0<12.2
Redhat Decision Manager=7.0
Redhat Software Collections
Redhat Enterprise Linux=8.0

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-2020-1720?

    CVE-2020-1720 is a vulnerability found in PostgreSQL's ALTER ... DEPENDS ON EXTENSION sub-commands that allows an authenticated attacker to perform unauthorized drop objects leading to database corruption.

  • How severe is CVE-2020-1720?

    CVE-2020-1720 is considered a high severity vulnerability with a severity score of 8.1 out of 10.

  • Which versions of PostgreSQL are affected by CVE-2020-1720?

    Versions 12.2, 11.7, 10.12, and 9.6.17 of PostgreSQL are affected by CVE-2020-1720.

  • How can an attacker exploit CVE-2020-1720?

    An authenticated attacker can exploit CVE-2020-1720 in certain configurations by using the ALTER ... DEPENDS ON EXTENSION command to drop objects such as functions and triggers, leading to database corruption.

  • What is the remedy for CVE-2020-1720?

    To fix CVE-2020-1720, you should upgrade to PostgreSQL versions 12.3, 11.9, 10.15, or 9.6.20, depending on the affected version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203