postgresql

Every one of the 15 is a mark on the map. Named now: 1 to 15, most at risk first.

1. A flaw was found in the way Postgresql allowed a user to modify the behavior of a query for other users. An attacker with a user account could use this flaw to execute code with t…CVE-2018-1058The PostgreSQL Global Development Group · 13% likely

   CWE-20

2. PostgreSQL versions 8.4 - 9.6 are vulnerable to information leak in pg_user_mappings view which discloses foreign server passwords to any user having USAGE privilege on the associ…CVE-2017-7486The PostgreSQL Global Development Group · 6.3% likely

   CWE-522

3. The to_char function in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to cause a…CVE-2015-0241PostgreSQL Global Development Group · 5.5% likely

   CWE-120

4. Stack-based buffer overflow in the *printf function implementations in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4…CVE-2015-0242PostgreSQL Global Development Group · 5.1% likely

   CWE-787

5. Multiple buffer overflows in contrib/pgcrypto in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allow remote authen…CVE-2015-0243PostgreSQL Global Development Group · 5.1% likely

   CWE-120

6. 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 li…CVE-2018-10915PostgreSQL Global Development Group · CVSS 8.5 · 5.1% likely

   CWE-665

7. The snprintf implementation in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7, and 9.4.x before 9.4.2 does not properly handle system-call…CVE-2015-3166PostgreSQL Global Development Group · 4.6% likely

   CWE-119

8. PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 does not properly handle errors while reading a protocol message, wh…CVE-2015-0244PostgreSQL Global Development Group · 4.4% likely

   CWE-89

9. contrib/pgcrypto in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7, and 9.4.x before 9.4.2 uses different error responses when an incorrect…CVE-2015-3167PostgreSQL Global Development Group · 4.1% likely

   CWE-200

10. It was found that some selectivity estimation functions in PostgreSQL before 9.2.21, 9.3.x before 9.3.17, 9.4.x before 9.4.12, 9.5.x before 9.5.7, and 9.6.x before 9.6.3 did not c…CVE-2017-7484The PostgreSQL Global Development Group · 2.6% likely

    CWE-285

11. PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to obtain sensitive column values…CVE-2014-8161PostgreSQL Global Development Group · 2.5% likely

    CWE-209

12. It was discovered that PostgreSQL versions before 10.5, 9.6.10, 9.5.14, 9.4.19, and 9.3.24 failed to properly check authorization on certain statements involved with "INSERT ... O…CVE-2018-10925PostgreSQL Global Development Group · CVSS 7.1 · 2.2% likely

    CWE-863

13. In PostgreSQL 9.3.x before 9.3.17, 9.4.x before 9.4.12, 9.5.x before 9.5.7, and 9.6.x before 9.6.3, it was found that the PGREQUIRESSL environment variable was no longer enforcing…CVE-2017-7485The PostgreSQL Global Development Group · 2.0% likely

    CWE-390

14. Memory disclosure vulnerability in table partitioning was found in postgresql 10.x before 10.2, allowing an authenticated attacker to read arbitrary bytes of server memory via pur…CVE-2018-1052The PostgreSQL Global Development Group · 1.8% likely

    CWE-200

15. In postgresql 9.3.x before 9.3.21, 9.4.x before 9.4.16, 9.5.x before 9.5.11, 9.6.x before 9.6.7 and 10.x before 10.2, pg_upgrade creates file in current working directory containi…CVE-2018-1053The PostgreSQL Global Development Group · 0.5% likely

    CWE-377

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.