CVE-2018-1058
CVE-2018-1058 Vulnerability Analysis & Exploit Intelligence
A flaw was found in the way Postgresql allowed a user to modify the behavior of a query for other users. An attacker with a user account could use this flaw to execute code with the permissions of superuser in the database. Versions 9.3 through 10 are affected.
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
Exploit code
public exploit, none observed
EPSS
13%
chance of exploitation in 30 days
CVSS base
Unscored
no source published a base score
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)
Weakness & attack patterns
- CWE-20
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1562.003Impair Defenses: Impair Command History Logging
- T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
- T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Indexed by
References
7 on the record
- bugzilla.redhat.com/show_bug.cgi?id=1547044
x_refsource_CONFIRM
- usn.ubuntu.com/3589-1/
vendor-advisory, x_refsource_UBUNTU
- www.securityfocus.com/bid/103221
vdb-entry, x_refsource_BID
- www.postgresql.org/about/news/1834/
x_refsource_CONFIRM
- access.redhat.com/errata/RHSA-2018:2511
vendor-advisory, x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2018:2566
vendor-advisory, x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2018:3816
vendor-advisory, x_refsource_REDHAT
Elsewhere on this site
- the postgresql global development groupevery CVE for this vendor
- CWE-20other 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.