{"id":"CVE-2018-1053","year":2018,"sequence":1053,"component":"client","score":6.7,"cvss_version":"3.0","vector":"AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H","first_published":"2018-02-08","source_url":"https://www.postgresql.org/support/security/CVE-2018-1053/","facts":{"affected":{"10":"10","9.3":"9.3","9.4":"9.4","9.5":"9.5","9.6":"9.6"},"component":"client","cvss_version":"3.0","description_en":"","first_published":"2018-02-08","fixed":{"10":"10.2","9.3":"9.3.21","9.4":"9.4.16","9.5":"9.5.11","9.6":"9.6.7"},"id":"CVE-2018-1053","introduced":{},"published":{"10":"2018-02-08","9.3":"2018-02-08","9.4":"2018-02-08","9.5":"2018-02-08","9.6":"2018-02-08"},"score":6.7,"title":"pg_upgrade creates file of sensitive metadata under prevailing umask","url":"https://www.postgresql.org/support/security/CVE-2018-1053/","vector":"AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H"},"reviewed_hash":"6a65a7884245936f6adaef8709d290d460e999dfce1ad78734fa7c9a324ed325","source_hash":"965b9e2323feab543f3cbeb74c418c3a5b43cbefc6594d2862ff0d24dcf8e6a2","text":null,"locales":["en"],"fixes":[{"major":"10","fixed_version":"10.2","introduced":null,"published_date":"2018-02-08","facts":{"fixed":"10.2","introduced":null,"published":"2018-02-08"}},{"major":"9.3","fixed_version":"9.3.21","introduced":null,"published_date":"2018-02-08","facts":{"fixed":"9.3.21","introduced":null,"published":"2018-02-08"}},{"major":"9.4","fixed_version":"9.4.16","introduced":null,"published_date":"2018-02-08","facts":{"fixed":"9.4.16","introduced":null,"published":"2018-02-08"}},{"major":"9.5","fixed_version":"9.5.11","introduced":null,"published_date":"2018-02-08","facts":{"fixed":"9.5.11","introduced":null,"published":"2018-02-08"}},{"major":"9.6","fixed_version":"9.6.7","introduced":null,"published_date":"2018-02-08","facts":{"fixed":"9.6.7","introduced":null,"published":"2018-02-08"}}],"legacy":[]}