First published: Mon May 06 2019(Updated: )
A vulnerability was found in PostgreSQL versions 11.x up to excluding 11.3, 10.x up to excluding 10.8, 9.6.x up to, excluding 9.6.13, 9.5.x up to, excluding 9.5.17. PostgreSQL maintains column statistics for tables. Certain statistics, such as histograms and lists of most common values, contain values taken from the column. PostgreSQL does not evaluate row security policies before consulting those statistics during query planning; an attacker can exploit this to read the most common values of certain columns. Affected columns are those for which the attacker has SELECT privilege and for which, in an ordinary query, row-level security prunes the set of rows visible to the attacker.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/rh-postgresql10-postgresql | <0:10.12-2.el7 | 0:10.12-2.el7 |
redhat/rh-postgresql96-postgresql | <0:9.6.19-1.el7 | 0:9.6.19-1.el7 |
redhat/postgresql | <11.3 | 11.3 |
redhat/postgresql | <10.8 | 10.8 |
redhat/postgresql | <9.6.13 | 9.6.13 |
redhat/postgresql | <9.5.17 | 9.5.17 |
PostgreSQL PostgreSQL | >=9.5.0<9.5.17 | |
PostgreSQL PostgreSQL | >=9.6.0<9.6.13 | |
PostgreSQL PostgreSQL | >=10.0<10.8 | |
PostgreSQL PostgreSQL | >=11.0<11.3 | |
openSUSE Leap | =15.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
The severity of CVE-2019-10130 is medium with a severity value of 4.3.
PostgreSQL versions 11.x up to excluding 11.3, 10.x up to excluding 10.8, 9.6.x up to, excluding 9.6.13, 9.5.x up to, excluding 9.5.17 are affected by CVE-2019-10130.
PostgreSQL maintains column statistics for tables.
PostgreSQL maintains certain statistics such as histograms and lists of most common values for tables.
You can find more information about CVE-2019-10130 at the following references: [Reference 1](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1709193), [Reference 2](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1709192), [Reference 3](https://www.postgresql.org/about/news/1939/).