Vulnerabilities · 2012 · Postgresql
CVE-2012-0866
Postgresql vulnerability
CREATE TRIGGER in PostgreSQL 8.3.x before 8.3.18, 8.4.x before 8.4.11, 9.0.x before 9.0.7, and 9.1.x before 9.1.3 does not properly check the execute permission for trigger functions marked SECURITY DEFINER, which allows remote authenticated users to execute otherwise restricted triggers on arbitrary data by installing the trigger on an attacker-owned table.
Affected products
Postgresql. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Postgresql runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- www.postgresql.org/about/news/1377/ · Vendor Advisory
- kb.juniper.net/InfoCenter/index?page=content&id=JSA10705
- lists.opensuse.org/opensuse-updates/2012-09/msg00060.html
- rhn.redhat.com/errata/RHSA-2012-0677.html
- rhn.redhat.com/errata/RHSA-2012-0678.html
- secunia.com/advisories/49272
- secunia.com/advisories/49273
- www.debian.org/security/2012/dsa-2418
- nvd.nist.gov/vuln/detail/CVE-2012-0866
- cve.org/CVERecord?id=CVE-2012-0866
More vulnerabilities in Postgresql products
CVE-2025-49146CVE-2024-10979CVE-2024-10978CVE-2024-10977CVE-2024-10976CVE-2024-7348CVE-2024-4317CVE-2024-1597All 168
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.