NVD / CVE Program· CNA redhat

CVE-2017-7546: PostgreSQL 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 attackers…

CriticalCVSS 9.8 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Plan (action score 57/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: 61.5% (FIRST EPSS); higher than 99.1% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: postgresql (Alpine:v3.10) 9.6.4-r0; postgresql14 (Alpine:v3.15) 9.6.4-r0; postgresql15 (Alpine:v3.17) 9.6.4-r0.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to postgresql (Alpine:v3.10) 9.6.4-r0; postgresql14 (Alpine:v3.15) 9.6.4-r0; postgresql15 (Alpine:v3.17) 9.6.4-r0 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 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 attackers to gain access to database accounts with an empty password.

Published: Aug 16, 2017
Updated: Jun 16, 2026
EPSS: 61.5% · 99th percentile
CWE: CWE-287

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 18 / 30 · 61.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 it

Noroxi 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 help

Affected 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 scan

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

Affected versions · NVD (20)

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

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:6::client	postgresql	before 0:8.4.20-8.el6_9	0:8.4.20-8.el6_9
Red Hat:enterprise_linux:6::client	postgresql-contrib	before 0:8.4.20-8.el6_9	0:8.4.20-8.el6_9
Red Hat:enterprise_linux:6::client	postgresql-debuginfo	before 0:8.4.20-8.el6_9	0:8.4.20-8.el6_9
Red Hat:enterprise_linux:6::client	postgresql-devel	before 0:8.4.20-8.el6_9	0:8.4.20-8.el6_9
Red Hat:enterprise_linux:6::client	postgresql-docs	before 0:8.4.20-8.el6_9	0:8.4.20-8.el6_9
Red Hat:enterprise_linux:6::client	postgresql-libs	before 0:8.4.20-8.el6_9	0:8.4.20-8.el6_9
Red Hat:enterprise_linux:6::client	postgresql-plperl	before 0:8.4.20-8.el6_9	0:8.4.20-8.el6_9
Red Hat:enterprise_linux:6::client	postgresql-plpython	before 0:8.4.20-8.el6_9	0:8.4.20-8.el6_9
Red Hat:enterprise_linux:6::client	postgresql-pltcl	before 0:8.4.20-8.el6_9	0:8.4.20-8.el6_9
Red Hat:enterprise_linux:6::client	postgresql-server	before 0:8.4.20-8.el6_9	0:8.4.20-8.el6_9
Red Hat:enterprise_linux:6::client	postgresql-test	before 0:8.4.20-8.el6_9	0:8.4.20-8.el6_9
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

+65

Same product

postgresql: all records

Other highest-scoring records for the same primary product.

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…
44Plan

Published before and after this one in the same product

← EarlierCVE-2017-7486May 12, 2017 · PostgreSQL versions 8.4 - 9.6 are vulnerable to information leak in pg_user_mappings view which discloses foreign server passwords to any…
32Monitor
← EarlierCVE-2016-0768Jun 6, 2017 · PostgreSQL PL/Java after 9.0 does not honor access controls on large objects.
30Monitor
Later →CVE-2017-7547Aug 16, 2017 · 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…
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
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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-20-094 · Feb 18, 2020(Postgresql Sunucu Güvenlik Güncellemesi)

All national notices →

Not on record for this CVE: 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.
No account or password is required.
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: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

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)

ATT&CK techniques

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:44 PM UTC

For records you follow, these changes also arrive as notifications. →

References

www.debian.org/security/2017/dsa-3935

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records