CVE-2018-10915
Last modified
CVE-2018-10915 is a high-severity vulnerability rated 8.5/10 on the CVSS scale. A vulnerability was found in libpq, the default PostgreSQL client library where libpq failed to properly reset its internal state between connections. If an affected version of libpq was used with "host" or "hostaddr" connection parameters from untrusted input, attackers could bypass client-side connection security features, obtain access to higher privileged connections or potentially cause other impact through SQL injection, by causing the PQescape() functions to malfunction. EPSS estimates a 5.15% chance of exploitation in the next 30 days.
Description
A vulnerability was found in libpq, the default PostgreSQL client library where libpq failed to properly reset its internal state between connections. If an affected version of libpq was used with "host" or "hostaddr" connection parameters from untrusted input, attackers could bypass client-side connection security features, obtain access to higher privileged connections or potentially cause other impact through SQL injection, by causing the PQescape() functions to malfunction. Postgresql versions before 10.5, 9.6.10, 9.5.14, 9.4.19, and 9.3.24 are affected.
Metrics
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Redhat | Openstack | 12 |
| Redhat | Openstack | 13 |
| Redhat | Virtualization | 4.0 |
| Redhat | Enterprise Linux Desktop | 7.0 |
| Redhat | Enterprise Linux Server | 7.0 |
| Redhat | Enterprise Linux Server Eus | 7.5 |
| Redhat | Enterprise Linux Workstation | 7.0 |
| Canonical | Ubuntu Linux | 14.04 |
| Canonical | Ubuntu Linux | 16.04 |
| Canonical | Ubuntu Linux | 18.04 |
| Debian | Debian Linux | 8.0 |
| Debian | Debian Linux | 9.0 |
| Postgresql | Postgresql | >= 9.3.0, < 9.3.24 |
| Postgresql | Postgresql | >= 9.4.0, < 9.4.19 |
| Postgresql | Postgresql | >= 9.5.0, < 9.5.14 |
| Postgresql | Postgresql | >= 9.6.0, < 9.6.10 |
| Postgresql | Postgresql | >= 10.0, < 10.5 |
References
- http://www.securityfocus.com/bid/105054Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1041446Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2018:2511Third Party Advisory
- https://access.redhat.com/errata/RHSA-2018:2557Third Party Advisory
- https://access.redhat.com/errata/RHSA-2018:2565Third Party Advisory
- https://access.redhat.com/errata/RHSA-2018:2566Third Party Advisory
- https://access.redhat.com/errata/RHSA-2018:2643Third Party Advisory
- https://access.redhat.com/errata/RHSA-2018:2721Third Party Advisory
- https://access.redhat.com/errata/RHSA-2018:2729Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10915Issue Tracking, Patch, Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2018/08/msg00012.htmlThird Party Advisory
- https://usn.ubuntu.com/3744-1/Third Party Advisory
- https://www.debian.org/security/2018/dsa-4269Third Party Advisory
- https://www.postgresql.org/about/news/1878/Vendor Advisory
- http://www.securityfocus.com/bid/105054Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1041446Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2018:2511Third Party Advisory
- https://access.redhat.com/errata/RHSA-2018:2557Third Party Advisory
- https://access.redhat.com/errata/RHSA-2018:2565Third Party Advisory
- https://access.redhat.com/errata/RHSA-2018:2566Third Party Advisory
- https://access.redhat.com/errata/RHSA-2018:2643Third Party Advisory
- https://access.redhat.com/errata/RHSA-2018:2721Third Party Advisory
- https://access.redhat.com/errata/RHSA-2018:2729Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10915Issue Tracking, Patch, Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2018/08/msg00012.htmlThird Party Advisory
- https://usn.ubuntu.com/3744-1/Third Party Advisory
- https://www.debian.org/security/2018/dsa-4269Third Party Advisory
- https://www.postgresql.org/about/news/1878/Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-10915?
How severe is CVE-2018-10915?
How do I fix CVE-2018-10915?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2018
- CVE-2018-1091In the flush_tmregs_to_thread function in arch/powerpc/kerne…
- CVE-2018-10910A bug in Bluez may allow for the Bluetooth Discoverable stat…4.5
- CVE-2018-10911A flaw was found in the way dic_unserialize function of glus…7.5
- CVE-2018-10912keycloak before version 4.0.0.final is vulnerable to a infin…4.9
- CVE-2018-10913An information disclosure vulnerability was discovered in gl…6.5
- CVE-2018-10914It was found that an attacker could issue a xattr request vi…6.5
- CVE-2018-10916It has been discovered that lftp up to and including version…5.3
- CVE-2018-10917pulp 2.16.x and possibly older is vulnerable to an improper …6.8
- CVE-2018-10918A null pointer dereference flaw was found in the way samba c…5.2
- CVE-2018-10919The Samba Active Directory LDAP server was vulnerable to an …4.3
- CVE-2018-1092The ext4_iget function in fs/ext4/inode.c in the Linux kerne…
- CVE-2018-10920Improper input validation bug in DNS resolver component of K…6.8
Are you affected by CVE-2018-10915?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
