CVE-2018-1115: postgresql before versions 10.4, 9.6.9 is vulnerable in the adminpack extension, the pg_catalog.pg_logfile_rotate() function doesn't follow…
Noroxi assessment
Priority: Monitor (action score 37/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: 3.8% (FIRST EPSS); higher than 90.2% 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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: postgresql (Alpine:v3.10) 10.4-r0; postgresql14 (Alpine:v3.15) 10.4-r0; postgresql15 (Alpine:v3.17) 10.4-r0.
- Severity is disputed: the assigning authority (CNA) scores it 4.2, NVD 9.1.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to postgresql (Alpine:v3.10) 10.4-r0; postgresql14 (Alpine:v3.15) 10.4-r0; postgresql15 (Alpine:v3.17) 10.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 before versions 10.4, 9.6.9 is vulnerable in the adminpack extension, the pg_catalog.pg_logfile_rotate() function doesn't follow the same ACLs than pg_rorate_logfile. If the adminpack is added to a database, an attacker able to connect to it could exploit this to force log rotation.
- Published
- May 10, 2018
- Updated
- Oct 8, 2026
- EPSS
- 3.8% · 90th percentile
- CWE
- CWE-732
Report tools
Action score
37
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.1
- CNA · redhat
- 4.2
- 4.9 point gap
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
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.
unspecified postgresql
- postegresql 10.4, postegresql 9.6.9affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- opensuse leap15.1
- postgresql postgresqlbefore 9.6.9
- postgresql postgresql10.0 and later · before 10.4
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 | from 10.0 · before 10.4-r0 | 10.4-r0 |
| Alpine:v3.15 | postgresql14 | before 10.4-r0 | 10.4-r0 |
| Alpine:v3.17 | postgresql15 | before 10.4-r0 | 10.4-r0 |
| Alpine:v3.4 | postgresql | from 10.0 · before 9.5.13-r0 | 9.5.13-r0 |
| Alpine:v3.5 | postgresql | from 10.0 · before 9.6.9-r0 | 9.6.9-r0 |
| openSUSE:Leap 15.1 | postgresql | before 12.0.1-lp151.6.9.1 | 12.0.1-lp151.6.9.1 |
| openSUSE:Leap 15.1 | postgresql10 | before 10.13-lp151.2.14.1 | 10.13-lp151.2.14.1 |
| openSUSE:Leap 15.1 | postgresql12 | before 12.3-lp151.2.1 | 12.3-lp151.2.1 |
| openSUSE:Leap 15.1 | postgresql96 | before 9.6.19-lp151.3.3.1 | 9.6.19-lp151.3.3.1 |
| openSUSE:Tumbleweed | postgresql10 | before 10.18-1.3 | 10.18-1.3 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-contrib | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-contrib-syspaths | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-debuginfo | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-devel | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-docs | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-libs | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-plperl | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-plpython | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-pltcl | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-server | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-server-syspaths | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-static | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
| Red Hat:rhel_software_collections:3::el6 | rh-postgresql96-postgresql-syspaths | before 0:9.6.10-1.el6 | 0:9.6.10-1.el6 |
+34
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-2017-14798Mar 1, 2018 · local privilege escalation in SUSE postgresql init script28Monitor
- ← EarlierCVE-2018-1058Mar 2, 2018 · A flaw was found in the way Postgresql allowed a user to modify the behavior of a query for other users.39Monitor
- Later →CVE-2018-10915Aug 9, 2018 · A vulnerability was found in libpq, the default PostgreSQL client library where libpq failed to properly reset its internal state between…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 | 10.4-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:postgresql14 | 10.4-r0 · Alpine:v3.15 | Package registry (OSV) |
| alpine:postgresql15 | 10.4-r0 · Alpine:v3.17 | Package registry (OSV) |
| opensuse:postgresql | 12.0.1-lp151.6.9.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| opensuse:postgresql10 | 10.13-lp151.2.14.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| opensuse:postgresql12 | 12.3-lp151.2.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| opensuse:postgresql96 | 9.6.19-lp151.3.3.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql | 0:10.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-contrib | 0:10.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-contrib-syspaths | 0:10.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-debuginfo | 0:10.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-devel | 0:10.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-docs | 0:10.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-libs | 0:10.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-plperl | 0:10.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-plpython | 0:10.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-pltcl | 0:10.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-server | 0:10.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-postgresql10-postgresql-server-syspaths | 0:10.5-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| suse:postgresql10 | 10.5-4.5.1 · SUSE:Linux Enterprise Module for Basesystem 15 | Package registry (OSV) |
| suse:postgresql96 | 9.6.9-3.19.1 · SUSE:Linux Enterprise Desktop 12 SP3 | Package registry (OSV) |
| suse:postgresql96-libs | 9.6.9-3.19.1 · SUSE:Linux Enterprise Desktop 12 SP3 | 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-620 · Aug 18, 2020(Postgresql Sunucu Güvenlik Güncellemesi)
- 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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- 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
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-732 · Incorrect Permission Assignment for Critical ResourceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Privilege AbuseCAPEC-122likelihood: High · Medium
- Directory IndexingCAPEC-127likelihood: High · Medium
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Exploiting Incorrectly Configured Access Control Security LevelsCAPEC-180likelihood: High · Medium
- Signing Malicious CodeCAPEC-206Very High
- Hijacking a privileged processCAPEC-234Medium
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
ATT&CK techniques
- File and Directory DiscoveryT1083
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Server Software Component: Terminal Services DLLT1505.005
- Abuse Elevation Control MechanismT1548
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Subvert Trust Controls:Code SigningT1553.002
- Compromise Client Software BinaryT1554
- Hijack Execution Flow:Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: ServicesFile Permissions WeaknessT1574.010
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.