VDB
CVE-2015-3167
CVE-2015-3167
PUBLISHED
Reported by redhat · Published November 20, 2019
contrib/pgcrypto in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7, and 9.4.x before 9.4.2 uses different error responses when an incorrect key is used, which makes it easier for attackers to obtain the key via a brute force attack.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| postgresql | postgresql | 9.4.2, 9.3.7, 9.2.11, 9.1.16, 9.0.20 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| PostgreSQL Global Development Group | PostgreSQL | before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11 |
| PostgreSQL Global Development Group | PostgreSQL | 9.0.20, 9.1.x, 9.2.x |
Timeline
- May 22, 2015 CVE Published
- Feb 4, 2022 EPSS Score (30 in total, the first dated here)
- Sep 8, 2025 CVE Updated
- Mar 5, 2026 Distribution Patch (5 in total, the first dated here)
- Mar 5, 2026 Security Advisory (4 in total, the first dated here)
- Oct 15, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2015-3167
vulnetix vdb fixes CVE-2015-3167
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2015-3167/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart