CVE-2017-7485: In PostgreSQL 9.3.x before 9.3.17, 9.4.x before 9.4.12, 9.5.x before 9.5.7, and 9.6.x before 9.6.3, it was found that the PGREQUIRESSL…
Noroxi assessment
Priority: Monitor (action score 24/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% (FIRST EPSS); higher than 81.4% 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. Special conditions such as timing or configuration are required.
- Fixed version: postgresql (Alpine:v3.10) 9.6.3-r0; postgresql14 (Alpine:v3.15) 9.6.3-r0; postgresql15 (Alpine:v3.17) 9.6.3-r0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to postgresql (Alpine:v3.10) 9.6.3-r0; postgresql14 (Alpine:v3.15) 9.6.3-r0; postgresql15 (Alpine:v3.17) 9.6.3-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
In PostgreSQL 9.3.x before 9.3.17, 9.4.x before 9.4.12, 9.5.x before 9.5.7, and 9.6.x before 9.6.3, it was found that the PGREQUIRESSL environment variable was no longer enforcing a SSL/TLS connection to a PostgreSQL server. An active Man-in-the-Middle attacker could use this flaw to strip the SSL/TLS protection from a connection between a client and a server.
- Published
- May 12, 2017
- Updated
- Jun 16, 2026
- EPSS
- 2.0% · 81th percentile
- CWE
- CWE-390
Report tools
Action score
24
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.0%
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 |
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.
The PostgreSQL Global Development Group PostgreSQL
- 9.3 - 9.6affected
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.3
- postgresql postgresql9.3.1
- postgresql postgresql9.3.10
- postgresql postgresql9.3.11
- postgresql postgresql9.3.12
- postgresql postgresql9.3.13
- postgresql postgresql9.3.14
- postgresql postgresql9.3.15
- postgresql postgresql9.3.16
- postgresql postgresql9.3.2
- postgresql postgresql9.3.3
- postgresql postgresql9.3.4
- postgresql postgresql9.3.5
- postgresql postgresql9.3.6
- postgresql postgresql9.3.7
- postgresql postgresql9.3.8
- postgresql postgresql9.3.9
- postgresql postgresql9.4
- postgresql postgresql9.4.1
- postgresql postgresql9.4.10
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.3-r0 | 9.6.3-r0 |
| Alpine:v3.15 | postgresql14 | before 9.6.3-r0 | 9.6.3-r0 |
| Alpine:v3.17 | postgresql15 | before 9.6.3-r0 | 9.6.3-r0 |
| Alpine:v3.3 | postgresql | before 9.4.12-r0 | 9.4.12-r0 |
| Alpine:v3.4 | postgresql | before 9.5.7-r0 | 9.5.7-r0 |
| Debian:8 | postgresql-9.4 | before 9.4.12-0+deb8u1 | 9.4.12-0+deb8u1 |
| Red Hat:network_satellite_managed_db:5.7::el6 | rh-postgresql95-runtime | before 0:2.2-3.el6 | 0:2.2-3.el6 |
| Red Hat:network_satellite_managed_db:5.7::el6 | spacewalk-base-minimal | before 0:2.3.2-35.el6sat | 0:2.3.2-35.el6sat |
| Red Hat:network_satellite_managed_db:5.7::el6 | spacewalk-dobby | before 0:2.3.2-35.el6sat | 0:2.3.2-35.el6sat |
| Red Hat:network_satellite_managed_db:5.7::el6 | spacewalk-postgresql-server | before 0:9.5-1.el6sat | 0:9.5-1.el6sat |
| Red Hat:network_satellite_managed_db:5.7::el6 | spacewalk-setup-postgresql | before 0:2.3.0-27.el6sat | 0:2.3.0-27.el6sat |
| Red Hat:network_satellite_managed_db:5.7::el6 | spacewalk-web | before 0:2.3.2-35.el6sat | 0:2.3.2-35.el6sat |
| Red Hat:network_satellite:5.7::el6 | spacewalk-backend | before 0:2.3.3-53.el6sat | 0:2.3.3-53.el6sat |
| Red Hat:network_satellite:5.7::el6 | spacewalk-backend-app | before 0:2.3.3-53.el6sat | 0:2.3.3-53.el6sat |
| Red Hat:network_satellite:5.7::el6 | spacewalk-backend-applet | before 0:2.3.3-53.el6sat | 0:2.3.3-53.el6sat |
| Red Hat:network_satellite:5.7::el6 | spacewalk-backend-config-files | before 0:2.3.3-53.el6sat | 0:2.3.3-53.el6sat |
| Red Hat:network_satellite:5.7::el6 | spacewalk-backend-config-files-common | before 0:2.3.3-53.el6sat | 0:2.3.3-53.el6sat |
| Red Hat:network_satellite:5.7::el6 | spacewalk-backend-config-files-tool | before 0:2.3.3-53.el6sat | 0:2.3.3-53.el6sat |
| Red Hat:network_satellite:5.7::el6 | spacewalk-backend-iss | before 0:2.3.3-53.el6sat | 0:2.3.3-53.el6sat |
| Red Hat:network_satellite:5.7::el6 | spacewalk-backend-iss-export | before 0:2.3.3-53.el6sat | 0:2.3.3-53.el6sat |
| Red Hat:network_satellite:5.7::el6 | spacewalk-backend-libs | before 0:2.3.3-53.el6sat | 0:2.3.3-53.el6sat |
| Red Hat:network_satellite:5.7::el6 | spacewalk-backend-package-push-server | before 0:2.3.3-53.el6sat | 0:2.3.3-53.el6sat |
| Red Hat:network_satellite:5.7::el6 | spacewalk-backend-server | before 0:2.3.3-53.el6sat | 0:2.3.3-53.el6sat |
| Red Hat:network_satellite:5.7::el6 | spacewalk-backend-sql | before 0:2.3.3-53.el6sat | 0:2.3.3-53.el6sat |
+67
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-2016-5424Dec 9, 2016 · PostgreSQL before 9.1.23, 9.2.x before 9.2.18, 9.3.x before 9.3.14, 9.4.x before 9.4.9, and 9.5.x before 9.5.4 might allow remote…29Monitor
- ← EarlierCVE-2017-7484May 12, 2017 · It was found that some selectivity estimation functions in PostgreSQL before 9.2.21, 9.3.x before 9.3.17, 9.4.x before 9.4.12, 9.5.x before…31Monitor
- Later →CVE-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
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.3-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:postgresql14 | 9.6.3-r0 · Alpine:v3.15 | Package registry (OSV) |
| alpine:postgresql15 | 9.6.3-r0 · Alpine:v3.17 | Package registry (OSV) |
| debian:postgresql-9.4 | 9.4.12-0+deb8u1 · Debian:8 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql | 0:9.5.7-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-contrib | 0:9.5.7-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-debuginfo | 0:9.5.7-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-devel | 0:9.5.7-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-docs | 0:9.5.7-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-libs | 0:9.5.7-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-plperl | 0:9.5.7-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-plpython | 0:9.5.7-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-pltcl | 0:9.5.7-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-server | 0:9.5.7-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-static | 0:9.5.7-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-postgresql95-postgresql-test | 0:9.5.7-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| suse:postgresql93 | 9.3.17-24.2 · SUSE:Linux Enterprise Server for SAP Applications 12 | Package registry (OSV) |
| suse:postgresql94 | 9.4.12-20.1 · SUSE:Linux Enterprise Desktop 12 SP2 | Package registry (OSV) |
| suse:postgresql94-libs | 9.4.12-20.1 · SUSE:Linux Enterprise Software Development Kit 12 SP2 | 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.
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)
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.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-390 · Detection of Error Condition Without ActionCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.