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.
CVE-2012-0866 is a security vulnerability that . Impacting 1 product from postgresql organizations running these solutions should prioritize assessment and patching.
Documented in 2012, this vulnerability occurred amid the cloud computing expansion era, where traditional network perimeter security models were being reevaluated. Organizations were transitioning from isolated infrastructure to interconnected systems, creating new attack surfaces that vulnerabilities like this could exploit.
2012-07-18T23:55:01.747
2025-04-11T00:51:21.963
Deferred
CVSSv2: 6.5 (MEDIUM)
AV:N/AC:L/Au:S/C:P/I:P/A:P
8.0
6.4
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | postgresql | postgresql | 8.3 | Yes |
| Application | postgresql | postgresql | 8.3.1 | Yes |
| Application | postgresql | postgresql | 8.3.2 | Yes |
| Application | postgresql | postgresql | 8.3.3 | Yes |
| Application | postgresql | postgresql | 8.3.4 | Yes |
| Application | postgresql | postgresql | 8.3.5 | Yes |
| Application | postgresql | postgresql | 8.3.6 | Yes |
| Application | postgresql | postgresql | 8.3.7 | Yes |
| Application | postgresql | postgresql | 8.3.8 | Yes |
| Application | postgresql | postgresql | 8.3.9 | Yes |
| Application | postgresql | postgresql | 8.3.10 | Yes |
| Application | postgresql | postgresql | 8.3.11 | Yes |
| Application | postgresql | postgresql | 8.3.12 | Yes |
| Application | postgresql | postgresql | 8.3.13 | Yes |
| Application | postgresql | postgresql | 8.3.14 | Yes |
| Application | postgresql | postgresql | 8.3.15 | Yes |
| Application | postgresql | postgresql | 8.3.16 | Yes |
| Application | postgresql | postgresql | 8.3.17 | Yes |
| Application | postgresql | postgresql | 8.4 | Yes |
| Application | postgresql | postgresql | 8.4.1 | Yes |
| Application | postgresql | postgresql | 8.4.2 | Yes |
| Application | postgresql | postgresql | 8.4.3 | Yes |
| Application | postgresql | postgresql | 8.4.4 | Yes |
| Application | postgresql | postgresql | 8.4.5 | Yes |
| Application | postgresql | postgresql | 8.4.6 | Yes |
| Application | postgresql | postgresql | 8.4.7 | Yes |
| Application | postgresql | postgresql | 8.4.8 | Yes |
| Application | postgresql | postgresql | 8.4.9 | Yes |
| Application | postgresql | postgresql | 8.4.10 | Yes |
| Application | postgresql | postgresql | 9.0 | Yes |
| Application | postgresql | postgresql | 9.0.1 | Yes |
| Application | postgresql | postgresql | 9.0.2 | Yes |
| Application | postgresql | postgresql | 9.0.3 | Yes |
| Application | postgresql | postgresql | 9.0.4 | Yes |
| Application | postgresql | postgresql | 9.0.5 | Yes |
| Application | postgresql | postgresql | 9.0.6 | Yes |
| Application | postgresql | postgresql | 9.1 | Yes |
| Application | postgresql | postgresql | 9.1.1 | Yes |
| Application | postgresql | postgresql | 9.1.2 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For postgresql's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.