Memory Corruption

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

1. 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

2. 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

3. 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

4. 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

5. 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

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.