CVE-2014-8161: PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated…
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.5% (FIRST EPSS); higher than 85% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: postgresql-8.4 (Debian:6.0) 8.4.22lts1-0+deb6u1; postgresql-9.1 (Debian:7) 9.1.15-0+deb7u1; postgresql (Red Hat:enterprise_linux:6::client) 0:8.4.20-2.el6_6.
Low priority for now. Upgrade to postgresql-8.4 (Debian:6.0) 8.4.22lts1-0+deb6u1; postgresql-9.1 (Debian:7) 9.1.15-0+deb7u1; postgresql (Red Hat:enterprise_linux:6::client) 0:8.4.20-2.el6_6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to obtain sensitive column values by triggering constraint violation and then reading the error message.
- Published
- Jan 27, 2020
- Updated
- Jun 16, 2026
- EPSS
- 2.5% · 85th percentile
- CWE
- CWE-209
Report tools
Action score
18
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is PostgreSQL on your server exposed to the internet?Run a port scan
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| postgresql | postgresql | cpe:2.3:a:postgresql:postgresql |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Using postgresql? Add it to your stack and be the first to know about CVEs like this one. (PostgreSQL)
Is PostgreSQL on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanVersions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
PostgreSQL Global Development Group PostgreSQL
- before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, 9.4.x before 9.4.1affected
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- postgresql postgresqlbefore 9.0.19
- postgresql postgresql9.1.0 and later · before 9.1.15
- postgresql postgresql9.2.0 and later · before 9.2.10
- postgresql postgresql9.3.0 and later · before 9.3.6
- postgresql postgresql9.4.0 and later · before 9.4.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:6.0 | postgresql-8.4 | before 8.4.22lts1-0+deb6u1 | 8.4.22lts1-0+deb6u1 |
| Debian:7 | postgresql-9.1 | before 9.1.15-0+deb7u1 | 9.1.15-0+deb7u1 |
| Red Hat:enterprise_linux:6::client | postgresql | before 0:8.4.20-2.el6_6 | 0:8.4.20-2.el6_6 |
| Red Hat:enterprise_linux:6::client | postgresql-contrib | before 0:8.4.20-2.el6_6 | 0:8.4.20-2.el6_6 |
| Red Hat:enterprise_linux:6::client | postgresql-debuginfo | before 0:8.4.20-2.el6_6 | 0:8.4.20-2.el6_6 |
| Red Hat:enterprise_linux:6::client | postgresql-devel | before 0:8.4.20-2.el6_6 | 0:8.4.20-2.el6_6 |
| Red Hat:enterprise_linux:6::client | postgresql-docs | before 0:8.4.20-2.el6_6 | 0:8.4.20-2.el6_6 |
| Red Hat:enterprise_linux:6::client | postgresql-libs | before 0:8.4.20-2.el6_6 | 0:8.4.20-2.el6_6 |
| Red Hat:enterprise_linux:6::client | postgresql-plperl | before 0:8.4.20-2.el6_6 | 0:8.4.20-2.el6_6 |
| Red Hat:enterprise_linux:6::client | postgresql-plpython | before 0:8.4.20-2.el6_6 | 0:8.4.20-2.el6_6 |
| Red Hat:enterprise_linux:6::client | postgresql-pltcl | before 0:8.4.20-2.el6_6 | 0:8.4.20-2.el6_6 |
| Red Hat:enterprise_linux:6::client | postgresql-server | before 0:8.4.20-2.el6_6 | 0:8.4.20-2.el6_6 |
| Red Hat:enterprise_linux:6::client | postgresql-test | before 0:8.4.20-2.el6_6 | 0:8.4.20-2.el6_6 |
| Red Hat:enterprise_linux:7::client | postgresql | before 0:9.2.10-2.el7_1 | 0:9.2.10-2.el7_1 |
| Red Hat:enterprise_linux:7::client | postgresql-contrib | before 0:9.2.10-2.el7_1 | 0:9.2.10-2.el7_1 |
| Red Hat:enterprise_linux:7::client | postgresql-debuginfo | before 0:9.2.10-2.el7_1 | 0:9.2.10-2.el7_1 |
| Red Hat:enterprise_linux:7::client | postgresql-devel | before 0:9.2.10-2.el7_1 | 0:9.2.10-2.el7_1 |
| Red Hat:enterprise_linux:7::client | postgresql-docs | before 0:9.2.10-2.el7_1 | 0:9.2.10-2.el7_1 |
| Red Hat:enterprise_linux:7::client | postgresql-libs | before 0:9.2.10-2.el7_1 | 0:9.2.10-2.el7_1 |
| Red Hat:enterprise_linux:7::client | postgresql-plperl | before 0:9.2.10-2.el7_1 | 0:9.2.10-2.el7_1 |
| Red Hat:enterprise_linux:7::client | postgresql-plpython | before 0:9.2.10-2.el7_1 | 0:9.2.10-2.el7_1 |
| Red Hat:enterprise_linux:7::client | postgresql-pltcl | before 0:9.2.10-2.el7_1 | 0:9.2.10-2.el7_1 |
| Red Hat:enterprise_linux:7::client | postgresql-server | before 0:9.2.10-2.el7_1 | 0:9.2.10-2.el7_1 |
| Red Hat:enterprise_linux:7::client | postgresql-test | before 0:9.2.10-2.el7_1 | 0:9.2.10-2.el7_1 |
+39
Same product
postgresql: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-7546PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allowing remote…57Plan
- CVE-2019-9193In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' group to…55Plan
- CVE-2020-25695A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24.49Plan
Published before and after this one in the same product
- ← EarlierCVE-2015-3166Nov 20, 2019 · The snprintf implementation 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.40Plan
- ← EarlierCVE-2015-3167Nov 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…31Monitor
- Later →CVE-2015-0241Jan 27, 2020 · The to_char function in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1…37Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:postgresql-8.4 | 8.4.22lts1-0+deb6u1 · Debian:6.0 | Package registry (OSV) |
| debian:postgresql-9.1 | 9.1.15-0+deb7u1 · Debian:7 | Package registry (OSV) |
| red hat:postgresql92-postgresql | 0:9.2.10-2.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| red hat:postgresql92-postgresql-contrib | 0:9.2.10-2.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| red hat:postgresql92-postgresql-debuginfo | 0:9.2.10-2.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| red hat:postgresql92-postgresql-devel | 0:9.2.10-2.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| red hat:postgresql92-postgresql-docs | 0:9.2.10-2.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| red hat:postgresql92-postgresql-libs | 0:9.2.10-2.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| red hat:postgresql92-postgresql-plperl | 0:9.2.10-2.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| red hat:postgresql92-postgresql-plpython | 0:9.2.10-2.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| red hat:postgresql92-postgresql-pltcl | 0:9.2.10-2.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| red hat:postgresql92-postgresql-server | 0:9.2.10-2.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| red hat:postgresql92-postgresql-test | 0:9.2.10-2.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| red hat:postgresql92-postgresql-upgrade | 0:9.2.10-2.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| suse:postgresql93 | 9.3.6-5.2 · SUSE:Linux Enterprise Desktop 12 | Package registry (OSV) |
| suse:postgresql93-libs | 9.3.6-5.1 · SUSE:Linux Enterprise Desktop 12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-209 · Generation of Error Message Containing Sensitive InformationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- www.postgresql.org/about/news/1569/
- www.postgresql.org/docs/9.4/static/release-9-4-1.html
- www.postgresql.org/docs/current/static/release-9-0-19.html
- www.postgresql.org/docs/current/static/release-9-1-15.html
- www.postgresql.org/docs/current/static/release-9-2-10.html
- www.postgresql.org/docs/current/static/release-9-3-6.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.