CVE-2018-10925
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering.
- Exploit odds
- 2.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 2.2% in the next 30 days (EPSS).
- Severity: 8.1 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 2.2% · EPSS, next 30 days
- Weakness
- CWE-863 · Incorrect authorization
- Record status
- Modified
Affected
- Canonical Ubuntu Linux 14.04
- Canonical Ubuntu Linux 16.04
- Canonical Ubuntu Linux 18.04
- Debian Linux 9.0
- PostgreSQL < 9.5.14
- PostgreSQL < 9.6.10
- PostgreSQL < 10.5
Attack profile CVSS 3.1 · 8.1
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2018-10925.md and follow it. Check whether this project is affected by CVE-2018-10925. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10925
- https://www.postgresql.org/about/news/1878/
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10925
- https://www.postgresql.org/about/news/1878/
References
- http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00043.html
- http://www.securityfocus.com/bid/105052
- http://www.securitytracker.com/id/1041446
- https://access.redhat.com/errata/RHSA-2018:2511
- https://access.redhat.com/errata/RHSA-2018:2565
- https://access.redhat.com/errata/RHSA-2018:2566
- https://access.redhat.com/errata/RHSA-2018:3816
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10925
- https://security.gentoo.org/glsa/201810-08
- https://usn.ubuntu.com/3744-1/
- https://www.debian.org/security/2018/dsa-4269
- https://www.postgresql.org/about/news/1878/
- http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00043.html
- http://www.securityfocus.com/bid/105052
- http://www.securitytracker.com/id/1041446
- https://access.redhat.com/errata/RHSA-2018:2511
- https://access.redhat.com/errata/RHSA-2018:2565
- https://access.redhat.com/errata/RHSA-2018:2566
- https://access.redhat.com/errata/RHSA-2018:3816
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10925
- https://security.gentoo.org/glsa/201810-08
- https://usn.ubuntu.com/3744-1/
- https://www.debian.org/security/2018/dsa-4269
- https://www.postgresql.org/about/news/1878/