CVE-2018-10925
CVE-2018-10925 Vulnerability Analysis & Exploit Intelligence
It was discovered that PostgreSQL versions before 10.5, 9.6.10, 9.5.14, 9.4.19, and 9.3.24 failed to properly check authorization on certain statements involved with "INSERT ... ON CONFLICT DO UPDATE". An attacker with "CREATE TABLE" privileges could exploit this to read arbitrary bytes server memory. If the attacker also had certain "INSERT" and limited "UPDATE" privileges to a particular table, they could exploit this to update other columns in the same table.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
2%
chance of exploitation in 30 days
CVSS base
7.1
HIGH
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.1 | CVSS 3.0 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-863
References
12 on the record
- security.gentoo.org/glsa/201810-08
vendor-advisory, x_refsource_GENTOO
- www.debian.org/security/2018/dsa-4269
vendor-advisory, x_refsource_DEBIAN
- www.securityfocus.com/bid/105052
vdb-entry, x_refsource_BID
- access.redhat.com/errata/RHSA-2018:2511
vendor-advisory, x_refsource_REDHAT
- usn.ubuntu.com/3744-1/
vendor-advisory, x_refsource_UBUNTU
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10925
x_refsource_CONFIRM
- access.redhat.com/errata/RHSA-2018:2566
vendor-advisory, x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2018:2565
vendor-advisory, x_refsource_REDHAT
Elsewhere on this site
- postgresql global development groupevery CVE for this vendor
- CWE-863other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.