Gentoo: GLSA-201811-24: PostgreSQL: SQL injection
Summary
A vulnerability was discovered in PostgreSQL's pg_upgrade and pg_dump.
Resolution
All PostgreSQL 9.3.x users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-db/postgresql-9.3.25"
All PostgreSQL 9.4.x users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-db/postgresql-9.4.20"
All PostgreSQL 9.5.x users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-db/postgresql-9.5.15"
All PostgreSQL 9.6.x users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-db/postgresql-9.6.11"
All PostgreSQL 10.x users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-db/postgresql-10.6"
All PostgreSQL 11.x users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-db/postgresql-11.1"
References
[ 1 ] CVE-2018-16850 https://nvd.nist.gov/vuln/detail/CVE-2018-16850
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201811-24
Concerns
Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.
Background
PostgreSQL is an open source object-relational database management system.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-db/postgresql *< 9.3.25 *>= 9.3.25 *< 9.4.20 *>= 9.4.20 *< 9.5.15 *>= 9.5.15 *< 9.6.11 *>= 9.6.11 *< 10.6 *>= 10.6 < 11.1 >= 11.1
Impact
===== An attacker, by enticing a user to process a specially crafted trigger definition, can execute arbitrary SQL statements with superuser privileges.
Workaround
There is no known workaround at this time.