PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to authorization flaw allowing remote authenticated attack
PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to authorization flaw allowing remote authenticated attackers to retrieve passwords from the user mappings defined by the foreign server owners without actually having the privileges to do so.
- Published
- Aug 16, 2017
- Updated
- Jun 16, 2026
- EPSS
- 5.6% · 93th percentile
- CWE
- CWE-522
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
37
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 5.6%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| postgresql | postgresql | cpe:2.3:a:postgresql:postgresql |
Using postgresql? Add it to your stack and be the first to know about CVEs like this one. (PostgreSQL)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- postgresql postgresql9.2
- postgresql postgresql9.2.1
- postgresql postgresql9.2.10
- postgresql postgresql9.2.11
- postgresql postgresql9.2.12
- postgresql postgresql9.2.13
- postgresql postgresql9.2.14
- postgresql postgresql9.2.15
- postgresql postgresql9.2.16
- postgresql postgresql9.2.17
- postgresql postgresql9.2.18
- postgresql postgresql9.2.19
- postgresql postgresql9.2.2
- postgresql postgresql9.2.20
- postgresql postgresql9.2.21
- postgresql postgresql9.2.3
- postgresql postgresql9.2.4
- postgresql postgresql9.2.5
- postgresql postgresql9.2.6
- postgresql postgresql9.2.7
Versions 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 postgresql
- 9.2.x before 9.2.22, 9.3.x before 9.3.18, 9.4.x before 9.4.13, 9.5.x before 9.5.8, 9.6.x before 9.6.4affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | postgresql | before 9.6.4-r0 | 9.6.4-r0 |
| Alpine:v3.15 | postgresql14 | before 9.6.4-r0 | 9.6.4-r0 |
| Alpine:v3.17 | postgresql15 | before 9.6.4-r0 | 9.6.4-r0 |
| Alpine:v3.3 | postgresql | before 9.4.13-r0 | 9.4.13-r0 |
| Alpine:v3.4 | postgresql | before 9.5.8-r0 | 9.5.8-r0 |
| Debian:7 | postgresql-9.1 | before 9.1.24lts2-0+deb7u1 | 9.1.24lts2-0+deb7u1 |
| Debian:8 | postgresql-9.4 | before 9.4.13-0+deb8u1 | 9.4.13-0+deb8u1 |
| Debian:9 | postgresql-9.6 | before 9.6.4-0+deb9u1 | 9.6.4-0+deb9u1 |
| Red Hat:enterprise_linux:7::client | postgresql | before 0:9.2.23-1.el7_4 | 0:9.2.23-1.el7_4 |
| Red Hat:enterprise_linux:7::client | postgresql-contrib | before 0:9.2.23-1.el7_4 | 0:9.2.23-1.el7_4 |
| Red Hat:enterprise_linux:7::client | postgresql-debuginfo | before 0:9.2.23-1.el7_4 | 0:9.2.23-1.el7_4 |
| Red Hat:enterprise_linux:7::client | postgresql-devel | before 0:9.2.23-1.el7_4 | 0:9.2.23-1.el7_4 |
| Red Hat:enterprise_linux:7::client | postgresql-docs | before 0:9.2.23-1.el7_4 | 0:9.2.23-1.el7_4 |
| Red Hat:enterprise_linux:7::client | postgresql-libs | before 0:9.2.23-1.el7_4 | 0:9.2.23-1.el7_4 |
| Red Hat:enterprise_linux:7::client | postgresql-plperl | before 0:9.2.23-1.el7_4 | 0:9.2.23-1.el7_4 |
| Red Hat:enterprise_linux:7::client | postgresql-plpython | before 0:9.2.23-1.el7_4 | 0:9.2.23-1.el7_4 |
| Red Hat:enterprise_linux:7::client | postgresql-pltcl | before 0:9.2.23-1.el7_4 | 0:9.2.23-1.el7_4 |
| Red Hat:enterprise_linux:7::client | postgresql-server | before 0:9.2.23-1.el7_4 | 0:9.2.23-1.el7_4 |
| Red Hat:enterprise_linux:7::client | postgresql-static | before 0:9.2.23-1.el7_4 | 0:9.2.23-1.el7_4 |
| Red Hat:enterprise_linux:7::client | postgresql-test | before 0:9.2.23-1.el7_4 | 0:9.2.23-1.el7_4 |
| Red Hat:enterprise_linux:7::client | postgresql-upgrade | before 0:9.2.23-1.el7_4 | 0:9.2.23-1.el7_4 |
| Red Hat:rhel_software_collections:2::el6 | rh-postgresql94-postgresql | before 0:9.4.14-1.el6 | 0:9.4.14-1.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-postgresql94-postgresql-contrib | before 0:9.4.14-1.el6 | 0:9.4.14-1.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-postgresql94-postgresql-debuginfo | before 0:9.4.14-1.el6 | 0:9.4.14-1.el6 |
+54
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 attackers57Plan
- 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
- CVE-2007-3280The Database Link library (dblink) in PostgreSQL 8.1 implements functions via CREATE statements that map to arbitrary libraries based on the44Plan
- CVE-2013-1899Argument injection vulnerability in PostgreSQL 9.2.x before 9.2.4, 9.1.x before 9.1.9, and 9.0.x before 9.0.13 allows remote attackers to ca42Plan
- CVE-2018-16850postgresql before versions 11.1, 10.6 is vulnerable to a to SQL injection in pg_upgrade and pg_dump via CREATE TRIGGER ...41Plan
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 |
|---|---|---|
| alpine:postgresql | 9.6.4-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:postgresql14 | 9.6.4-r0 · Alpine:v3.15 | Package registry (OSV) |
| alpine:postgresql15 | 9.6.4-r0 · Alpine:v3.17 | Package registry (OSV) |
| debian:postgresql-9.1 | 9.1.24lts2-0+deb7u1 · Debian:7 | Package registry (OSV) |
| debian:postgresql-9.4 | 9.4.13-0+deb8u1 · Debian:8 | Package registry (OSV) |
| debian:postgresql-9.6 | 9.6.4-0+deb9u1 · Debian:9 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql | 0:9.5.9-1.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-contrib | 0:9.5.9-1.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-debuginfo | 0:9.5.9-1.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-devel | 0:9.5.9-1.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-docs | 0:9.5.9-1.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-libs | 0:9.5.9-1.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-plperl | 0:9.5.9-1.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-plpython | 0:9.5.9-1.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-pltcl | 0:9.5.9-1.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-server | 0:9.5.9-1.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-static | 0:9.5.9-1.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-test | 0:9.5.9-1.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| suse:postgresql93 | 9.3.18-25.5.1 · SUSE:Linux Enterprise Server for SAP Applications 12 | Package registry (OSV) |
| suse:postgresql94 | 9.4.13-0.23.5.1 · SUSE:Linux Enterprise Point of Sale 11 SP3 | Package registry (OSV) |
| suse:postgresql94-libs | 9.4.13-0.23.5.1 · SUSE:Linux Enterprise Software Development Kit 11 SP4 | Package registry (OSV) |
| suse:postgresql96 | 9.6.4-3.6.1 · SUSE:OpenStack Cloud 6 | Package registry (OSV) |
| suse:postgresql96-libs | 9.6.4-3.6.1 · SUSE:OpenStack Cloud 6 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-522 · Insufficiently Protected CredentialsCVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
Attack patterns (CAPEC)
- Session SidejackingCAPEC-102likelihood: High · High
- Signature Spoofing by Key TheftCAPEC-474likelihood: Medium · High
- Password Recovery ExploitationCAPEC-50likelihood: Medium · High
- KerberoastingCAPEC-509High
- Modify Existing ServiceCAPEC-551
- Remote Services with Stolen CredentialsCAPEC-555Very High
- Use of Known Domain CredentialsCAPEC-560likelihood: High · High
- Windows Admin Shares with Stolen CredentialsCAPEC-561
ATT&CK techniques
- Remote ServicesT1021
- Remote Services:SMB/Windows Admin SharesT1021.002
- Valid AccountsT1078
- Brute Force:Credential StuffingT1110.004
- Email Collection:Remote Email CollectionT1114.002
- External Remote ServicesT1133
- Create or Modify System ProcessT1543
- Use Alternate Authentication Material:Pass The HashT1550.002
- Use Alternate Authentication Material:Pass The TicketT1550.003
- Unsecured Credentials: Private KeysT1552.004
- Steal or Forge Kerberos TicketsT1558
- Steal or Forge Kerberos Tickets:KerberoastingT1558.003
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.debian.org/security/2017/dsa-3935
- www.debian.org/security/2017/dsa-3936
- www.securityfocus.com/bid/100275
- www.securitytracker.com/id/1039142
- access.redhat.com/errata/RHSA-2017:2677
- access.redhat.com/errata/RHSA-2017:2678
- access.redhat.com/errata/RHSA-2017:2728
- security.gentoo.org/glsa/201710-06
- www.postgresql.org/about/news/1772/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.