ID CVE-2018-1115
Summary postgresql before versions 10.4, 9.6.9 is vulnerable in the adminpack extension, the pg_catalog.pg_logfile_rotate() function doesn't follow the same ACLs than pg_rorate_logfile. If the adminpack is added to a database, an attacker able to connect to it could exploit this to force log rotation.
References
Vulnerable Configurations
  • PostgreSQL
    cpe:2.3:a:postgresql:postgresql
  • PostgreSQL for Debian
    cpe:2.3:a:postgresql:postgresql:-:-:-:-:-:debian
  • PostgreSQL for Ubuntu
    cpe:2.3:a:postgresql:postgresql:-:-:-:-:-:ubuntu
  • PostgreSQL 6.3
    cpe:2.3:a:postgresql:postgresql:6.3
  • PostgreSQL 6.4
    cpe:2.3:a:postgresql:postgresql:6.4
  • PostgreSQL 6.5
    cpe:2.3:a:postgresql:postgresql:6.5
  • PostgreSQL 7.0
    cpe:2.3:a:postgresql:postgresql:7.0
  • PostgreSQL 7.1
    cpe:2.3:a:postgresql:postgresql:7.1
  • PostgreSQL 7.2
    cpe:2.3:a:postgresql:postgresql:7.2
  • PostgreSQL 7.3
    cpe:2.3:a:postgresql:postgresql:7.3
  • PostgreSQL 7.3.0
    cpe:2.3:a:postgresql:postgresql:7.3.0
  • PostgreSQL 7.3.1
    cpe:2.3:a:postgresql:postgresql:7.3.1
  • PostgreSQL 7.3.2
    cpe:2.3:a:postgresql:postgresql:7.3.2
  • PostgreSQL 7.3.3
    cpe:2.3:a:postgresql:postgresql:7.3.3
  • PostgreSQL 7.3.4
    cpe:2.3:a:postgresql:postgresql:7.3.4
  • PostgreSQL 7.3.5
    cpe:2.3:a:postgresql:postgresql:7.3.5
  • PostgreSQL 7.3.6
    cpe:2.3:a:postgresql:postgresql:7.3.6
  • PostgreSQL 7.3.7
    cpe:2.3:a:postgresql:postgresql:7.3.7
  • PostgreSQL 7.3.8
    cpe:2.3:a:postgresql:postgresql:7.3.8
  • PostgreSQL 7.3.9
    cpe:2.3:a:postgresql:postgresql:7.3.9
  • PostgreSQL 7.3.10
    cpe:2.3:a:postgresql:postgresql:7.3.10
  • PostgreSQL 7.3.11
    cpe:2.3:a:postgresql:postgresql:7.3.11
  • PostgreSQL 7.3.12
    cpe:2.3:a:postgresql:postgresql:7.3.12
  • PostgreSQL 7.3.13
    cpe:2.3:a:postgresql:postgresql:7.3.13
  • PostgreSQL 7.3.14
    cpe:2.3:a:postgresql:postgresql:7.3.14
  • PostgreSQL 7.3.15
    cpe:2.3:a:postgresql:postgresql:7.3.15
  • PostgreSQL 7.3.16
    cpe:2.3:a:postgresql:postgresql:7.3.16
  • PostgreSQL 7.3.17
    cpe:2.3:a:postgresql:postgresql:7.3.17
  • PostgreSQL 7.3.18
    cpe:2.3:a:postgresql:postgresql:7.3.18
  • PostgreSQL 7.3.19
    cpe:2.3:a:postgresql:postgresql:7.3.19
  • PostgreSQL 7.3.20
    cpe:2.3:a:postgresql:postgresql:7.3.20
  • PostgreSQL 7.3.21
    cpe:2.3:a:postgresql:postgresql:7.3.21
  • PostgreSQL PostgreSQL 7.4
    cpe:2.3:a:postgresql:postgresql:7.4
  • PostgreSQL PostgreSQL 7.4.1
    cpe:2.3:a:postgresql:postgresql:7.4.1
  • PostgreSQL PostgreSQL 7.4.2
    cpe:2.3:a:postgresql:postgresql:7.4.2
  • PostgreSQL PostgreSQL 7.4.3
    cpe:2.3:a:postgresql:postgresql:7.4.3
  • PostgreSQL PostgreSQL 7.4.4
    cpe:2.3:a:postgresql:postgresql:7.4.4
  • PostgreSQL PostgreSQL 7.4.5
    cpe:2.3:a:postgresql:postgresql:7.4.5
  • PostgreSQL PostgreSQL 7.4.6
    cpe:2.3:a:postgresql:postgresql:7.4.6
  • PostgreSQL PostgreSQL 7.4.7
    cpe:2.3:a:postgresql:postgresql:7.4.7
  • PostgreSQL PostgreSQL 7.4.8
    cpe:2.3:a:postgresql:postgresql:7.4.8
  • PostgreSQL PostgreSQL 7.4.9
    cpe:2.3:a:postgresql:postgresql:7.4.9
  • PostgreSQL PostgreSQL 7.4.10
    cpe:2.3:a:postgresql:postgresql:7.4.10
  • PostgreSQL PostgreSQL 7.4.11
    cpe:2.3:a:postgresql:postgresql:7.4.11
  • PostgreSQL PostgreSQL 7.4.12
    cpe:2.3:a:postgresql:postgresql:7.4.12
  • PostgreSQL PostgreSQL 7.4.13
    cpe:2.3:a:postgresql:postgresql:7.4.13
  • PostgreSQL PostgreSQL 7.4.14
    cpe:2.3:a:postgresql:postgresql:7.4.14
  • PostgreSQL PostgreSQL 7.4.15
    cpe:2.3:a:postgresql:postgresql:7.4.15
  • PostgreSQL PostgreSQL 7.4.16
    cpe:2.3:a:postgresql:postgresql:7.4.16
  • PostgreSQL PostgreSQL 7.4.17
    cpe:2.3:a:postgresql:postgresql:7.4.17
  • PostgreSQL PostgreSQL 7.4.18
    cpe:2.3:a:postgresql:postgresql:7.4.18
  • PostgreSQL PostgreSQL 7.4.19
    cpe:2.3:a:postgresql:postgresql:7.4.19
  • PostgreSQL PostgreSQL 7.4.20
    cpe:2.3:a:postgresql:postgresql:7.4.20
  • PostgreSQL PostgreSQL 7.4.21
    cpe:2.3:a:postgresql:postgresql:7.4.21
  • PostgreSQL PostgreSQL 7.4.22
    cpe:2.3:a:postgresql:postgresql:7.4.22
  • PostgreSQL PostgreSQL 7.4.23
    cpe:2.3:a:postgresql:postgresql:7.4.23
  • PostgreSQL PostgreSQL 7.4.24
    cpe:2.3:a:postgresql:postgresql:7.4.24
  • PostgreSQL PostgreSQL 7.4.25
    cpe:2.3:a:postgresql:postgresql:7.4.25
  • PostgreSQL PostgreSQL 7.4.26
    cpe:2.3:a:postgresql:postgresql:7.4.26
  • PostgreSQL PostgreSQL 7.4.27
    cpe:2.3:a:postgresql:postgresql:7.4.27
  • PostgreSQL PostgreSQL 7.4.28
    cpe:2.3:a:postgresql:postgresql:7.4.28
  • PostgreSQL PostgreSQL 7.4.29
    cpe:2.3:a:postgresql:postgresql:7.4.29
  • PostgreSQL 7.4.30
    cpe:2.3:a:postgresql:postgresql:7.4.30
  • PostgreSQL 8.0
    cpe:2.3:a:postgresql:postgresql:8.0
  • PostgreSQL PostgreSQL 8.0.1
    cpe:2.3:a:postgresql:postgresql:8.0.1
  • PostgreSQL PostgreSQL 8.0.2
    cpe:2.3:a:postgresql:postgresql:8.0.2
  • PostgreSQL PostgreSQL 8.0.3
    cpe:2.3:a:postgresql:postgresql:8.0.3
  • PostgreSQL PostgreSQL 8.0.4
    cpe:2.3:a:postgresql:postgresql:8.0.4
  • PostgreSQL PostgreSQL 8.0.5
    cpe:2.3:a:postgresql:postgresql:8.0.5
  • PostgreSQL PostgreSQL 8.0.6
    cpe:2.3:a:postgresql:postgresql:8.0.6
  • PostgreSQL PostgreSQL 8.0.7
    cpe:2.3:a:postgresql:postgresql:8.0.7
  • PostgreSQL PostgreSQL 8.0.8
    cpe:2.3:a:postgresql:postgresql:8.0.8
  • PostgreSQL PostgreSQL 8.0.9
    cpe:2.3:a:postgresql:postgresql:8.0.9
  • PostgreSQL PostgreSQL 8.0.10
    cpe:2.3:a:postgresql:postgresql:8.0.10
  • PostgreSQL PostgreSQL 8.0.11
    cpe:2.3:a:postgresql:postgresql:8.0.11
  • PostgreSQL PostgreSQL 8.0.12
    cpe:2.3:a:postgresql:postgresql:8.0.12
  • PostgreSQL PostgreSQL 8.0.13
    cpe:2.3:a:postgresql:postgresql:8.0.13
  • PostgreSQL PostgreSQL 8.0.14
    cpe:2.3:a:postgresql:postgresql:8.0.14
  • PostgreSQL PostgreSQL 8.0.15
    cpe:2.3:a:postgresql:postgresql:8.0.15
  • PostgreSQL PostgreSQL 8.0.16
    cpe:2.3:a:postgresql:postgresql:8.0.16
  • PostgreSQL PostgreSQL 8.0.17
    cpe:2.3:a:postgresql:postgresql:8.0.17
  • PostgreSQL PostgreSQL 8.0.18
    cpe:2.3:a:postgresql:postgresql:8.0.18
  • PostgreSQL PostgreSQL 8.0.19
    cpe:2.3:a:postgresql:postgresql:8.0.19
  • PostgreSQL PostgreSQL 8.0.20
    cpe:2.3:a:postgresql:postgresql:8.0.20
  • PostgreSQL PostgreSQL 8.0.21
    cpe:2.3:a:postgresql:postgresql:8.0.21
  • PostgreSQL PostgreSQL 8.0.22
    cpe:2.3:a:postgresql:postgresql:8.0.22
  • PostgreSQL PostgreSQL 8.0.23
    cpe:2.3:a:postgresql:postgresql:8.0.23
  • PostgreSQL PostgreSQL 8.0.24
    cpe:2.3:a:postgresql:postgresql:8.0.24
  • PostgreSQL PostgreSQL 8.0.25
    cpe:2.3:a:postgresql:postgresql:8.0.25
  • PostgreSQL 8.0.26
    cpe:2.3:a:postgresql:postgresql:8.0.26
  • PostgreSQL 8.1
    cpe:2.3:a:postgresql:postgresql:8.1
  • PostgreSQL 8.1.1
    cpe:2.3:a:postgresql:postgresql:8.1.1
  • PostgreSQL 8.1.2
    cpe:2.3:a:postgresql:postgresql:8.1.2
  • PostgreSQL 8.1.3
    cpe:2.3:a:postgresql:postgresql:8.1.3
  • PostgreSQL 8.1.4
    cpe:2.3:a:postgresql:postgresql:8.1.4
  • PostgreSQL 8.1.5
    cpe:2.3:a:postgresql:postgresql:8.1.5
  • PostgreSQL 8.1.6
    cpe:2.3:a:postgresql:postgresql:8.1.6
  • PostgreSQL 8.1.7
    cpe:2.3:a:postgresql:postgresql:8.1.7
  • PostgreSQL 8.1.8
    cpe:2.3:a:postgresql:postgresql:8.1.8
  • PostgreSQL 8.1.9
    cpe:2.3:a:postgresql:postgresql:8.1.9
  • PostgreSQL 8.1.10
    cpe:2.3:a:postgresql:postgresql:8.1.10
  • PostgreSQL 8.1.11
    cpe:2.3:a:postgresql:postgresql:8.1.11
  • PostgreSQL 8.1.12
    cpe:2.3:a:postgresql:postgresql:8.1.12
  • PostgreSQL 8.1.13
    cpe:2.3:a:postgresql:postgresql:8.1.13
  • PostgreSQL 8.1.14
    cpe:2.3:a:postgresql:postgresql:8.1.14
  • PostgreSQL 8.1.15
    cpe:2.3:a:postgresql:postgresql:8.1.15
  • PostgreSQL 8.1.16
    cpe:2.3:a:postgresql:postgresql:8.1.16
  • PostgreSQL 8.1.17
    cpe:2.3:a:postgresql:postgresql:8.1.17
  • PostgreSQL 8.1.18
    cpe:2.3:a:postgresql:postgresql:8.1.18
  • PostgreSQL 8.1.19
    cpe:2.3:a:postgresql:postgresql:8.1.19
  • PostgreSQL 8.1.20
    cpe:2.3:a:postgresql:postgresql:8.1.20
  • PostgreSQL 8.1.21
    cpe:2.3:a:postgresql:postgresql:8.1.21
  • PostgreSQL 8.1.22
    cpe:2.3:a:postgresql:postgresql:8.1.22
  • PostgreSQL 8.2
    cpe:2.3:a:postgresql:postgresql:8.2
  • PostgreSQL 8.2.1
    cpe:2.3:a:postgresql:postgresql:8.2.1
  • PostgreSQL 8.2.2
    cpe:2.3:a:postgresql:postgresql:8.2.2
  • PostgreSQL 8.2.3
    cpe:2.3:a:postgresql:postgresql:8.2.3
  • PostgreSQL 8.2.4
    cpe:2.3:a:postgresql:postgresql:8.2.4
  • PostgreSQL 8.2.5
    cpe:2.3:a:postgresql:postgresql:8.2.5
  • PostgreSQL 8.2.6
    cpe:2.3:a:postgresql:postgresql:8.2.6
  • PostgreSQL 8.2.7
    cpe:2.3:a:postgresql:postgresql:8.2.7
  • PostgreSQL 8.2.8
    cpe:2.3:a:postgresql:postgresql:8.2.8
  • PostgreSQL 8.2.9
    cpe:2.3:a:postgresql:postgresql:8.2.9
  • PostgreSQL 8.2.10
    cpe:2.3:a:postgresql:postgresql:8.2.10
  • PostgreSQL 8.2.11
    cpe:2.3:a:postgresql:postgresql:8.2.11
  • PostgreSQL 8.2.12
    cpe:2.3:a:postgresql:postgresql:8.2.12
  • PostgreSQL 8.2.13
    cpe:2.3:a:postgresql:postgresql:8.2.13
  • PostgreSQL 8.2.14
    cpe:2.3:a:postgresql:postgresql:8.2.14
  • PostgreSQL 8.2.15
    cpe:2.3:a:postgresql:postgresql:8.2.15
  • PostgreSQL 8.2.16
    cpe:2.3:a:postgresql:postgresql:8.2.16
  • PostgreSQL 8.2.17
    cpe:2.3:a:postgresql:postgresql:8.2.17
  • PostgreSQL 8.2.18
    cpe:2.3:a:postgresql:postgresql:8.2.18
  • PostgreSQL 8.3
    cpe:2.3:a:postgresql:postgresql:8.3
  • PostgreSQL 8.3.1
    cpe:2.3:a:postgresql:postgresql:8.3.1
  • PostgreSQL 8.3.2
    cpe:2.3:a:postgresql:postgresql:8.3.2
  • PostgreSQL 8.3.3
    cpe:2.3:a:postgresql:postgresql:8.3.3
  • PostgreSQL 8.3.4
    cpe:2.3:a:postgresql:postgresql:8.3.4
  • PostgreSQL 8.3.5
    cpe:2.3:a:postgresql:postgresql:8.3.5
  • PostgreSQL 8.3.6
    cpe:2.3:a:postgresql:postgresql:8.3.6
  • PostgreSQL 8.3.7
    cpe:2.3:a:postgresql:postgresql:8.3.7
  • PostgreSQL 8.3.8
    cpe:2.3:a:postgresql:postgresql:8.3.8
  • PostgreSQL 8.3.9
    cpe:2.3:a:postgresql:postgresql:8.3.9
  • PostgreSQL 8.3.10
    cpe:2.3:a:postgresql:postgresql:8.3.10
  • PostgreSQL 8.3.11
    cpe:2.3:a:postgresql:postgresql:8.3.11
  • PostgreSQL 8.3.12
    cpe:2.3:a:postgresql:postgresql:8.3.12
  • PostgreSQL 8.3.13
    cpe:2.3:a:postgresql:postgresql:8.3.13
  • PostgreSQL 8.3.14
    cpe:2.3:a:postgresql:postgresql:8.3.14
  • PostgreSQL 8.3.15
    cpe:2.3:a:postgresql:postgresql:8.3.15
  • PostgreSQL 8.3.16
    cpe:2.3:a:postgresql:postgresql:8.3.16
  • PostgreSQL 8.3.17
    cpe:2.3:a:postgresql:postgresql:8.3.17
  • PostgreSQL 8.3.18
    cpe:2.3:a:postgresql:postgresql:8.3.18
  • PostgreSQL 8.3.19
    cpe:2.3:a:postgresql:postgresql:8.3.19
  • PostgreSQL 8.3.20
    cpe:2.3:a:postgresql:postgresql:8.3.20
  • PostgreSQL 8.3.21
    cpe:2.3:a:postgresql:postgresql:8.3.21
  • PostgreSQL 8.3.22
    cpe:2.3:a:postgresql:postgresql:8.3.22
  • PostgreSQL 8.4
    cpe:2.3:a:postgresql:postgresql:8.4
  • PostgreSQL 8.4.1
    cpe:2.3:a:postgresql:postgresql:8.4.1
  • PostgreSQL 8.4.2
    cpe:2.3:a:postgresql:postgresql:8.4.2
  • PostgreSQL 8.4.3
    cpe:2.3:a:postgresql:postgresql:8.4.3
  • PostgreSQL 8.4.4
    cpe:2.3:a:postgresql:postgresql:8.4.4
  • PostgreSQL 8.4.5
    cpe:2.3:a:postgresql:postgresql:8.4.5
  • PostgreSQL 8.4.6
    cpe:2.3:a:postgresql:postgresql:8.4.6
  • PostgreSQL 8.4.7
    cpe:2.3:a:postgresql:postgresql:8.4.7
  • PostgreSQL 8.4.8
    cpe:2.3:a:postgresql:postgresql:8.4.8
  • PostgreSQL 8.4.9
    cpe:2.3:a:postgresql:postgresql:8.4.9
  • PostgreSQL 8.4.10
    cpe:2.3:a:postgresql:postgresql:8.4.10
  • PostgreSQL 8.4.11
    cpe:2.3:a:postgresql:postgresql:8.4.11
  • PostgreSQL 8.4.12
    cpe:2.3:a:postgresql:postgresql:8.4.12
  • PostgreSQL 8.4.13
    cpe:2.3:a:postgresql:postgresql:8.4.13
  • PostgreSQL 8.4.14
    cpe:2.3:a:postgresql:postgresql:8.4.14
  • PostgreSQL 8.4.15
    cpe:2.3:a:postgresql:postgresql:8.4.15
  • PostgreSQL 8.4.16
    cpe:2.3:a:postgresql:postgresql:8.4.16
  • PostgreSQL PostgreSQL 8.4.17
    cpe:2.3:a:postgresql:postgresql:8.4.17
  • PostgreSQL PostgreSQL 8.4.18
    cpe:2.3:a:postgresql:postgresql:8.4.18
  • PostgreSQL PostgreSQL 8.4.19
    cpe:2.3:a:postgresql:postgresql:8.4.19
  • PostgreSQL PostgreSQL 8.4.20
    cpe:2.3:a:postgresql:postgresql:8.4.20
  • PostgreSQL 8.4.21
    cpe:2.3:a:postgresql:postgresql:8.4.21
  • PostgreSQL 8.4.22
    cpe:2.3:a:postgresql:postgresql:8.4.22
  • PostgreSQL 9.0
    cpe:2.3:a:postgresql:postgresql:9.0
  • PostgreSQL 9.0.1
    cpe:2.3:a:postgresql:postgresql:9.0.1
  • PostgreSQL 9.0.2
    cpe:2.3:a:postgresql:postgresql:9.0.2
  • PostgreSQL 9.0.3
    cpe:2.3:a:postgresql:postgresql:9.0.3
  • PostgreSQL 9.0.4
    cpe:2.3:a:postgresql:postgresql:9.0.4
  • PostgreSQL 9.0.5
    cpe:2.3:a:postgresql:postgresql:9.0.5
  • PostgreSQL 9.0.6
    cpe:2.3:a:postgresql:postgresql:9.0.6
  • PostgreSQL 9.0.7
    cpe:2.3:a:postgresql:postgresql:9.0.7
  • PostgreSQL 9.0.8
    cpe:2.3:a:postgresql:postgresql:9.0.8
  • PostgreSQL 9.0.9
    cpe:2.3:a:postgresql:postgresql:9.0.9
  • PostgreSQL 9.0.10
    cpe:2.3:a:postgresql:postgresql:9.0.10
  • PostgreSQL 9.0.11
    cpe:2.3:a:postgresql:postgresql:9.0.11
  • PostgreSQL 9.0.12
    cpe:2.3:a:postgresql:postgresql:9.0.12
  • PostgreSQL PostgreSQL 9.0.13
    cpe:2.3:a:postgresql:postgresql:9.0.13
  • PostgreSQL PostgreSQL 9.0.14
    cpe:2.3:a:postgresql:postgresql:9.0.14
  • PostgreSQL PostgreSQL 9.0.15
    cpe:2.3:a:postgresql:postgresql:9.0.15
  • PostgreSQL PostgreSQL 9.0.16
    cpe:2.3:a:postgresql:postgresql:9.0.16
  • PostgreSQL 9.0.17
    cpe:2.3:a:postgresql:postgresql:9.0.17
  • PostgreSQL 9.0.18
    cpe:2.3:a:postgresql:postgresql:9.0.18
  • PostgreSQL 9.0.20
    cpe:2.3:a:postgresql:postgresql:9.0.20
  • PostgreSQL 9.0.21
    cpe:2.3:a:postgresql:postgresql:9.0.21
  • PostgreSQL 9.0.23
    cpe:2.3:a:postgresql:postgresql:9.0.23
  • PostgreSQL 9.1
    cpe:2.3:a:postgresql:postgresql:9.1
  • PostgreSQL 9.1.1
    cpe:2.3:a:postgresql:postgresql:9.1.1
  • PostgreSQL 9.1.2
    cpe:2.3:a:postgresql:postgresql:9.1.2
  • PostgreSQL 9.1.3
    cpe:2.3:a:postgresql:postgresql:9.1.3
  • PostgreSQL 9.1.4
    cpe:2.3:a:postgresql:postgresql:9.1.4
  • PostgreSQL 9.1.5
    cpe:2.3:a:postgresql:postgresql:9.1.5
  • PostgreSQL 9.1.6
    cpe:2.3:a:postgresql:postgresql:9.1.6
  • PostgreSQL 9.1.7
    cpe:2.3:a:postgresql:postgresql:9.1.7
  • PostgreSQL 9.1.8
    cpe:2.3:a:postgresql:postgresql:9.1.8
  • PostgreSQL PostgreSQL 9.1.9
    cpe:2.3:a:postgresql:postgresql:9.1.9
  • PostgreSQL PostgreSQL 9.1.10
    cpe:2.3:a:postgresql:postgresql:9.1.10
  • PostgreSQL PostgreSQL 9.1.11
    cpe:2.3:a:postgresql:postgresql:9.1.11
  • PostgreSQL PostgreSQL 9.1.12
    cpe:2.3:a:postgresql:postgresql:9.1.12
  • PostgreSQL PostgreSQL 9.1.19
    cpe:2.3:a:postgresql:postgresql:9.1.19
  • PostgreSQL 9.1.20
    cpe:2.3:a:postgresql:postgresql:9.1.20
  • PostgreSQL 9.1.21
    cpe:2.3:a:postgresql:postgresql:9.1.21
  • PostgreSQL 9.1.22
    cpe:2.3:a:postgresql:postgresql:9.1.22
  • PostgreSQL 9.1.23
    cpe:2.3:a:postgresql:postgresql:9.1.23
  • PostgreSQL 9.1.24
    cpe:2.3:a:postgresql:postgresql:9.1.24
  • PostgreSQL 9.2
    cpe:2.3:a:postgresql:postgresql:9.2
  • PostgreSQL 9.2.1
    cpe:2.3:a:postgresql:postgresql:9.2.1
  • PostgreSQL 9.2.2
    cpe:2.3:a:postgresql:postgresql:9.2.2
  • PostgreSQL PostgreSQL 9.2.3
    cpe:2.3:a:postgresql:postgresql:9.2.3
  • PostgreSQL PostgreSQL 9.2.4
    cpe:2.3:a:postgresql:postgresql:9.2.4
  • PostgreSQL PostgreSQL 9.2.5
    cpe:2.3:a:postgresql:postgresql:9.2.5
  • PostgreSQL PostgreSQL 9.2.6
    cpe:2.3:a:postgresql:postgresql:9.2.6
  • PostgreSQL PostgreSQL 9.2.7
    cpe:2.3:a:postgresql:postgresql:9.2.7
  • PostgreSQL PostgreSQL 9.2.14
    cpe:2.3:a:postgresql:postgresql:9.2.14
  • PostgreSQL 9.2.15
    cpe:2.3:a:postgresql:postgresql:9.2.15
  • PostgreSQL 9.2.16
    cpe:2.3:a:postgresql:postgresql:9.2.16
  • PostgreSQL 9.2.17
    cpe:2.3:a:postgresql:postgresql:9.2.17
  • PostgreSQL 9.2.18
    cpe:2.3:a:postgresql:postgresql:9.2.18
  • PostgreSQL 9.2.19
    cpe:2.3:a:postgresql:postgresql:9.2.19
  • PostgreSQL 9.2.20
    cpe:2.3:a:postgresql:postgresql:9.2.20
  • PostgreSQL 9.2.21
    cpe:2.3:a:postgresql:postgresql:9.2.21
  • PostgreSQL 9.2.22
    cpe:2.3:a:postgresql:postgresql:9.2.22
  • PostgreSQL 9.2.23
    cpe:2.3:a:postgresql:postgresql:9.2.23
  • PostgreSQL 9.2.24
    cpe:2.3:a:postgresql:postgresql:9.2.24
  • PostgreSQL PostgreSQL 9.3
    cpe:2.3:a:postgresql:postgresql:9.3
  • PostgreSQL 9.3.0
    cpe:2.3:a:postgresql:postgresql:9.3.0
  • PostgreSQL PostgreSQL 9.3.1
    cpe:2.3:a:postgresql:postgresql:9.3.1
  • PostgreSQL PostgreSQL 9.3.2
    cpe:2.3:a:postgresql:postgresql:9.3.2
  • PostgreSQL PostgreSQL 9.3.3
    cpe:2.3:a:postgresql:postgresql:9.3.3
  • PostgreSQL 9.3.4
    cpe:2.3:a:postgresql:postgresql:9.3.4
  • PostgreSQL 9.3.5
    cpe:2.3:a:postgresql:postgresql:9.3.5
  • PostgreSQL 9.3.6
    cpe:2.3:a:postgresql:postgresql:9.3.6
  • PostgreSQL 9.3.7
    cpe:2.3:a:postgresql:postgresql:9.3.7
  • PostgreSQL 9.3.8
    cpe:2.3:a:postgresql:postgresql:9.3.8
  • PostgreSQL 9.3.9
    cpe:2.3:a:postgresql:postgresql:9.3.9
  • PostgreSQL 9.3.10
    cpe:2.3:a:postgresql:postgresql:9.3.10
  • PostgreSQL 9.3.11
    cpe:2.3:a:postgresql:postgresql:9.3.11
  • PostgreSQL 9.3.12
    cpe:2.3:a:postgresql:postgresql:9.3.12
  • PostgreSQL 9.3.13
    cpe:2.3:a:postgresql:postgresql:9.3.13
  • PostgreSQL 9.3.14
    cpe:2.3:a:postgresql:postgresql:9.3.14
  • PostgreSQL 9.3.15
    cpe:2.3:a:postgresql:postgresql:9.3.15
  • PostgreSQL 9.3.16
    cpe:2.3:a:postgresql:postgresql:9.3.16
  • PostgreSQL 9.3.17
    cpe:2.3:a:postgresql:postgresql:9.3.17
  • PostgreSQL 9.3.18
    cpe:2.3:a:postgresql:postgresql:9.3.18
  • PostgreSQL 9.3.19
    cpe:2.3:a:postgresql:postgresql:9.3.19
  • PostgreSQL 9.3.20
    cpe:2.3:a:postgresql:postgresql:9.3.20
  • PostgreSQL 9.3.21
    cpe:2.3:a:postgresql:postgresql:9.3.21
  • PostgreSQL 9.3.22
    cpe:2.3:a:postgresql:postgresql:9.3.22
  • PostgreSQL PostgreSQL 9.4
    cpe:2.3:a:postgresql:postgresql:9.4
  • PostgreSQL 9.4.0
    cpe:2.3:a:postgresql:postgresql:9.4.0
  • PostgreSQL 9.4.1
    cpe:2.3:a:postgresql:postgresql:9.4.1
  • PostgreSQL 9.4.2
    cpe:2.3:a:postgresql:postgresql:9.4.2
  • PostgreSQL 9.4.3
    cpe:2.3:a:postgresql:postgresql:9.4.3
  • PostgreSQL 9.4.4
    cpe:2.3:a:postgresql:postgresql:9.4.4
  • PostgreSQL PostgreSQL 9.4.5
    cpe:2.3:a:postgresql:postgresql:9.4.5
  • PostgreSQL 9.4.6
    cpe:2.3:a:postgresql:postgresql:9.4.6
  • PostgreSQL 9.4.7
    cpe:2.3:a:postgresql:postgresql:9.4.7
  • PostgreSQL 9.4.8
    cpe:2.3:a:postgresql:postgresql:9.4.8
  • PostgreSQL 9.4.9
    cpe:2.3:a:postgresql:postgresql:9.4.9
  • PostgreSQL 9.4.10
    cpe:2.3:a:postgresql:postgresql:9.4.10
  • PostgreSQL 9.4.11
    cpe:2.3:a:postgresql:postgresql:9.4.11
  • PostgreSQL 9.4.12
    cpe:2.3:a:postgresql:postgresql:9.4.12
  • PostgreSQL 9.4.13
    cpe:2.3:a:postgresql:postgresql:9.4.13
  • PostgreSQL 9.4.14
    cpe:2.3:a:postgresql:postgresql:9.4.14
  • PostgreSQL 9.4.15
    cpe:2.3:a:postgresql:postgresql:9.4.15
  • PostgreSQL 9.4.16
    cpe:2.3:a:postgresql:postgresql:9.4.16
  • PostgreSQL PostgreSQL 9.5
    cpe:2.3:a:postgresql:postgresql:9.5
  • PostgreSQL 9.5.0
    cpe:2.3:a:postgresql:postgresql:9.5.0
  • PostgreSQL 9.5.1
    cpe:2.3:a:postgresql:postgresql:9.5.1
  • PostgreSQL 9.5.2
    cpe:2.3:a:postgresql:postgresql:9.5.2
  • PostgreSQL 9.5.3
    cpe:2.3:a:postgresql:postgresql:9.5.3
  • PostgreSQL 9.5.4
    cpe:2.3:a:postgresql:postgresql:9.5.4
  • PostgreSQL 9.5.5
    cpe:2.3:a:postgresql:postgresql:9.5.5
  • PostgreSQL 9.5.6
    cpe:2.3:a:postgresql:postgresql:9.5.6
  • PostgreSQL 9.5.7
    cpe:2.3:a:postgresql:postgresql:9.5.7
  • PostgreSQL 9.5.8
    cpe:2.3:a:postgresql:postgresql:9.5.8
  • PostgreSQL 9.5.9
    cpe:2.3:a:postgresql:postgresql:9.5.9
  • PostgreSQL 9.5.10
    cpe:2.3:a:postgresql:postgresql:9.5.10
  • PostgreSQL 9.5.11
    cpe:2.3:a:postgresql:postgresql:9.5.11
  • PostgreSQL 9.6
    cpe:2.3:a:postgresql:postgresql:9.6
  • PostgreSQL 9.6.0
    cpe:2.3:a:postgresql:postgresql:9.6.0
  • PostgreSQL 9.6.1
    cpe:2.3:a:postgresql:postgresql:9.6.1
  • PostgreSQL 9.6.2
    cpe:2.3:a:postgresql:postgresql:9.6.2
  • PostgreSQL 9.6.3
    cpe:2.3:a:postgresql:postgresql:9.6.3
  • PostgreSQL 9.6.4
    cpe:2.3:a:postgresql:postgresql:9.6.4
  • PostgreSQL 9.6.5
    cpe:2.3:a:postgresql:postgresql:9.6.5
  • PostgreSQL 9.6.6
    cpe:2.3:a:postgresql:postgresql:9.6.6
  • PostgreSQL 9.6.7
    cpe:2.3:a:postgresql:postgresql:9.6.7
  • PostgreSQL 9.6.8
    cpe:2.3:a:postgresql:postgresql:9.6.8
  • PostgreSQL 10.0
    cpe:2.3:a:postgresql:postgresql:10.0
  • PostgreSQL 10.1
    cpe:2.3:a:postgresql:postgresql:10.1
  • PostgreSQL 10.2
    cpe:2.3:a:postgresql:postgresql:10.2
  • PostgreSQL 10.3
    cpe:2.3:a:postgresql:postgresql:10.3
CVSS
Base: 6.4
Impact:
Exploitability:
CWE CWE-16
CAPEC
nessus via4
  • NASL family Databases
    NASL id POSTGRESQL_20181115.NASL
    description The version of PostgreSQL installed on the remote host is 9.3.x prior to 9.3.23, 9.4.x prior to 9.4.18, 9.5.x prior to 9.5.13, or 9.6.x prior to 9.6.9, or 10.3.x. As such, it is potentially affected by Insecure ACL Remote Issue
    last seen 2019-02-21
    modified 2018-08-16
    plugin id 110288
    published 2018-06-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=110288
    title PostgreSQL 9.3 < 9.3.23 / 9.4 < 9.4.18 / 9.5 < 9.5.13 / 9.6 < 9.6.9 / 10.3 Insecure ACL Remote Issue
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2018-BD6F9237B5.NASL
    description update to 9.6.9 per release notes https://www.postgresql.org/docs/9.6/static/release-9-6-9.html Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-18
    plugin id 109972
    published 2018-05-23
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=109972
    title Fedora 26 : postgresql (2018-bd6f9237b5)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2018-955.NASL
    description This update for postgresql10 fixes the following issues : PostgreSQL 10 was updated to 10.5 : - https://www.postgresql.org/about/news/1851/ - https://www.postgresql.org/docs/current/static/release-10-5.html A dump/restore is not required for those running 10.X. However, if you use the adminpack extension, you should update it as per the first changelog entry below. Also, if the function marking mistakes mentioned in the second and third changelog entries below affect you, you will want to take steps to correct your database catalogs. Security issues fixed : - CVE-2018-1115: Remove public execute privilege from contrib/adminpack's pg_logfile_rotate() function pg_logfile_rotate() is a deprecated wrapper for the core function pg_rotate_logfile(). When that function was changed to rely on SQL privileges for access control rather than a hard-coded superuser check, pg_logfile_rotate() should have been updated as well, but the need for this was missed. Hence, if adminpack is installed, any user could request a logfile rotation, creating a minor security issue. After installing this update, administrators should update adminpack by performing ALTER EXTENSION adminpack UPDATE in each database in which adminpack is installed (bsc#1091610). - CVE-2018-10915: 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 have bypassed client-side connection security features, obtain access to higher privileged connections or potentially cause other impact SQL injection, by causing the PQescape() functions to malfunction (bsc#1104199) - CVE-2018-10925: Add missing authorization check on certain statements involved with 'INSERT ... ON CONFLICT DO UPDATE'. An attacker with 'CREATE TABLE' privileges could have exploited this to read arbitrary bytes server memory. If the attacker also had certain 'INSERT' and limited 'UPDATE' privileges to a particular table, they could have exploited this to update other columns in the same table (bsc#1104202). This update was imported from the SUSE:SLE-15:Update update project.
    last seen 2019-02-21
    modified 2018-12-18
    plugin id 112269
    published 2018-09-04
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=112269
    title openSUSE Security Update : postgresql10 (openSUSE-2018-955)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2018-696.NASL
    description This update for postgresql95 fixes the following issues : - Update to PostgreSQL 9.5.13 : - https://www.postgresql.org/docs/9.5/static/release-9-5-13.html A dump/restore is not required for those running 9.5.X. However, if the function marking mistakes mentioned belowpg_logfile_rotate affect you, you will want to take steps to correct your database catalogs. The functions query_to_xml, cursor_to_xml, cursor_to_xmlschema, query_to_xmlschema, and query_to_xml_and_xmlschema should be marked volatile because they execute user-supplied queries that might contain volatile operations. They were not, leading to a risk of incorrect query optimization. This has been repaired for new installations by correcting the initial catalog data, but existing installations will continue to contain the incorrect markings. Practical use of these functions seems to pose little hazard, but in case of trouble, it can be fixed by manually updating these functions' pg_proc entries, for example: ALTER FUNCTION pg_catalog.query_to_xml(text, boolean, boolean, text) VOLATILE. (Note that that will need to be done in each database of the installation.) Another option is to pg_upgrade the database to a version containing the corrected initial data. Security issue fixed : - CVE-2018-1115: Remove public execute privilege from contrib/adminpack's pg_logfile_rotate() function pg_logfile_rotate() is a deprecated wrapper for the core function pg_rotate_logfile(). When that function was changed to rely on SQL privileges for access control rather than a hard-coded superuser check, pg_logfile_rotate() should have been updated as well, but the need for this was missed. Hence, if adminpack is installed, any user could request a logfile rotation, creating a minor security issue. After installing this update, administrators should update adminpack by performing ALTER EXTENSION adminpack UPDATE in each database in which adminpack is installed. (bsc#1091610)
    last seen 2019-02-21
    modified 2018-12-18
    plugin id 110955
    published 2018-07-09
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=110955
    title openSUSE Security Update : postgresql95 (openSUSE-2018-696)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_SU-2018-1695-1.NASL
    description PostgreSQL was updated to 9.6.9 fixing bugs and security issues: Release notes : - https://www.postgresql.org/about/news/1851/ - https://www.postgresql.org/docs/current/static/release-9-6-9.html A dump/restore is not required for those running 9.6.X. However, if you use the adminpack extension, you should update it as per the first changelog entry below. Also, if the function marking mistakes mentioned in the second and third changelog entries below affect you, you will want to take steps to correct your database catalogs. Security issue fixed : - CVE-2018-1115: Remove public execute privilege from contrib/adminpack's pg_logfile_rotate() function pg_logfile_rotate() is a deprecated wrapper for the core function pg_rotate_logfile(). When that function was changed to rely on SQL privileges for access control rather than a hard-coded superuser check, pg_logfile_rotate() should have been updated as well, but the need for this was missed. Hence, if adminpack is installed, any user could request a logfile rotation, creating a minor security issue. After installing this update, administrators should update adminpack by performing ALTER EXTENSION adminpack UPDATE in each database in which adminpack is installed. (bsc#1091610) Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-18
    plugin id 110548
    published 2018-06-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=110548
    title SUSE SLED12 / SLES12 Security Update : postgresql96 (SUSE-SU-2018:1695-1)
  • NASL family Amazon Linux Local Security Checks
    NASL id ALA_ALAS-2018-1119.NASL
    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 were 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.(CVE-2018-10915) It was discovered that PostgreSQL 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.(CVE-2018-10925) It was found that pg_catalog.pg_logfile_rotate(), from the adminpack extension, did not follow the same ACLs than pg_rorate_logfile. If the adminpack is added to a database, an attacker able to connect to it could use this flaw to force log rotation.(CVE-2018-1115 )
    last seen 2019-02-21
    modified 2018-12-07
    plugin id 119478
    published 2018-12-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=119478
    title Amazon Linux AMI : postgresql96 (ALAS-2018-1119)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2018-638.NASL
    description PostgreSQL was updated to 9.6.9 fixing bugs and security issues : Release notes : - https://www.postgresql.org/about/news/1851/ - https://www.postgresql.org/docs/current/static/release-9-6-9.html A dump/restore is not required for those running 9.6.X. However, if you use the adminpack extension, you should update it as per the first changelog entry below. Also, if the function marking mistakes mentioned in the second and third changelog entries below affect you, you will want to take steps to correct your database catalogs. Security issue fixed : - CVE-2018-1115: Remove public execute privilege from contrib/adminpack's pg_logfile_rotate() function pg_logfile_rotate() is a deprecated wrapper for the core function pg_rotate_logfile(). When that function was changed to rely on SQL privileges for access control rather than a hard-coded superuser check, pg_logfile_rotate() should have been updated as well, but the need for this was missed. Hence, if adminpack is installed, any user could request a logfile rotation, creating a minor security issue. After installing this update, administrators should update adminpack by performing ALTER EXTENSION adminpack UPDATE in each database in which adminpack is installed. (bsc#1091610) This update was imported from the SUSE:SLE-12:Update update project.
    last seen 2019-02-21
    modified 2018-12-18
    plugin id 110588
    published 2018-06-18
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=110588
    title openSUSE Security Update : postgresql96 (openSUSE-2018-638)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2018-937C789F2A.NASL
    description update to 9.6.9 per release notes: https://www.postgresql.org/docs/9.6/static/release-9-6-9.html Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-18
    plugin id 109971
    published 2018-05-23
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=109971
    title Fedora 27 : postgresql (2018-937c789f2a)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_SU-2018-2564-1.NASL
    description This update for postgresql10 fixes the following issues : PostgreSQL 10 was updated to 10.5 : https://www.postgresql.org/about/news/1851/ https://www.postgresql.org/docs/current/static/release-10-5.html A dump/restore is not required for those running 10.X. However, if you use the adminpack extension, you should update it as per the first changelog entry below. Also, if the function marking mistakes mentioned in the second and third changelog entries below affect you, you will want to take steps to correct your database catalogs. Security issues fixed: CVE-2018-1115: Remove public execute privilege from contrib/adminpack's pg_logfile_rotate() function pg_logfile_rotate() is a deprecated wrapper for the core function pg_rotate_logfile(). When that function was changed to rely on SQL privileges for access control rather than a hard-coded superuser check, pg_logfile_rotate() should have been updated as well, but the need for this was missed. Hence, if adminpack is installed, any user could request a logfile rotation, creating a minor security issue. After installing this update, administrators should update adminpack by performing ALTER EXTENSION adminpack UPDATE in each database in which adminpack is installed (bsc#1091610). CVE-2018-10915: 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 have bypassed client-side connection security features, obtain access to higher privileged connections or potentially cause other impact SQL injection, by causing the PQescape() functions to malfunction (bsc#1104199) CVE-2018-10925: Add missing authorization check on certain statements involved with 'INSERT ... ON CONFLICT DO UPDATE'. An attacker with 'CREATE TABLE' privileges could have exploited this to read arbitrary bytes server memory. If the attacker also had certain 'INSERT' and limited 'UPDATE' privileges to a particular table, they could have exploited this to update other columns in the same table (bsc#1104202). Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2019-01-02
    plugin id 120090
    published 2019-01-02
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=120090
    title SUSE SLED15 / SLES15 Security Update : postgresql10 (SUSE-SU-2018:2564-1)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2018-08550A9006.NASL
    description update to 10.4 per release notes: https://www.postgresql.org/docs/10/static/release-10-4.html Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2019-01-03
    plugin id 120220
    published 2019-01-03
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=120220
    title Fedora 28 : postgresql (2018-08550a9006)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201810-08.NASL
    description The remote host is affected by the vulnerability described in GLSA-201810-08 (PostgreSQL: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in PostgreSQL. Please review the referenced CVE identifiers for details. In addition it was discovered that Gentoo’s PostgreSQL installation suffered from a privilege escalation vulnerability due to a runscript which called OpenRC’s checkpath() on a user controlled path and allowed user running PostgreSQL to kill arbitrary processes via PID file manipulation. Impact : A remote attacker could bypass certain client-side connection security features, read arbitrary server memory or alter certain data. In addition, a local attacker could gain privileges or cause a Denial of Service condition by killing arbitrary processes. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-10-31
    plugin id 118508
    published 2018-10-31
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=118508
    title GLSA-201810-08 : PostgreSQL: Multiple vulnerabilities
redhat via4
advisories
  • rhsa
    id RHSA-2018:2565
  • rhsa
    id RHSA-2018:2566
refmap via4
bid 104285
confirm
gentoo GLSA-201810-08
Last major update 10-05-2018 - 15:29
Published 10-05-2018 - 15:29
Last modified 21-03-2019 - 11:11
Back to Top