Memory Corruption

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

1. An issue was discovered in Tiny C Compiler (aka TinyCC or TCC) 0.9.27. Compiling a crafted source file leads to a one-byte out-of-bounds write in the gsym_addr function in x86_64-…CVE-2019-12495Tinycc · 1.2% likely

   CWE-787

2. An issue was discovered in Tiny C Compiler (aka TinyCC or TCC) 0.9.27. Compiling a crafted source file leads to an 1 byte out of bounds write in the end_macro function in tccpp.c.CVE-2019-9754Tinycc · 0.9% likely

   CWE-787

3. An issue was discovered in Tiny C Compiler (aka TinyCC or TCC) 0.9.27. Compiling a crafted source file leads to an 8 byte out of bounds write in the asm_parse_directive function i…CVE-2018-20376Tinycc · 0.7% likely

   CWE-787

4. An issue was discovered in Tiny C Compiler (aka TinyCC or TCC) 0.9.27. Compiling a crafted source file leads to an 8 byte out of bounds write in the sym_pop function in tccgen.c.CVE-2018-20375Tinycc · 0.7% likely

   CWE-787

5. An issue was discovered in Tiny C Compiler (aka TinyCC or TCC) 0.9.27. Compiling a crafted source file leads to an 8 byte out of bounds write in the use_section1 function in tccas…CVE-2018-20374Tinycc · 0.7% likely

   CWE-787

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.