Memory Corruption

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

1. com_line() in command.c in gnuplot 5.4 leads to an out-of-bounds-write from strncpy() that may lead to arbitrary code execution.CVE-2020-25412Gnuplot · 2.6% likely

   CWE-787

2. An issue was discovered in cairo.trm in Gnuplot 5.2.5. This issue allows an attacker to conduct a buffer overflow with an arbitrary amount of data in the cairotrm_options function…CVE-2018-19492Gnuplot · 1.8% likely

   CWE-119

3. An issue was discovered in post.trm in Gnuplot 5.2.5. This issue allows an attacker to conduct a buffer overflow with an arbitrary amount of data in the PS_options function. This…CVE-2018-19491Gnuplot · 1.8% likely

   CWE-119

4. An issue was discovered in datafile.c in Gnuplot 5.2.5. This issue allows an attacker to conduct a heap-based buffer overflow with an arbitrary amount of data in df_generate_ascii…CVE-2018-19490Gnuplot · 1.8% likely

   CWE-787

5. gnuplot 5.5 is affected by double free when executing print_set_output. This may result in context-dependent arbitrary code execution.CVE-2020-25559Gnuplot · 1.6% likely

   CWE-415

6. gnuplot v5.5 was discovered to contain a buffer overflow via the function plotrequest().CVE-2020-25969Gnuplot · 1.0% likely

   CWE-120

7. An uninitialized stack variable vulnerability in load_tic_series() in set.c in gnuplot 5.2.rc1 allows an attacker to cause Denial of Service (Segmentation fault and Memory Corrupt…CVE-2017-9670Gnuplot · 0.9% likely

   CWE-824

8. Buffer overflow in the French documentation patch for Gnuplot 3.7 in SuSE Linux before 8.0 allows local users to execute arbitrary code as root via unknown attack vectors.CVE-2002-2259Gnuplot · 0.5% 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.