Libextractor

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

1. Multiple heap-based buffer overflows in Libextractor 0.5.13 and earlier allow remote attackers to execute arbitrary code via (1) the asf_read_header function in the ASF plugin (pl…CVE-2006-2458Libextractor · 9.2% likely
2. Xpdf, as used in products such as gpdf, kpdf, pdftohtml, poppler, teTeX, CUPS, libextractor, and others, allows attackers to cause a denial of service (infinite loop) via streams…CVE-2005-3625Libextractor · 3.8% likely

   CWE-399

3. Xpdf, as used in products such as gpdf, kpdf, pdftohtml, poppler, teTeX, CUPS, libextractor, and others, allows attackers to cause a denial of service (crash) via a crafted FlateD…CVE-2005-3626Libextractor · 3.4% likely

   CWE-399

4. The CCITTFaxStream::CCITTFaxStream function in Stream.cc for xpdf, gpdf, kpdf, pdftohtml, poppler, teTeX, CUPS, libextractor, and others allows attackers to corrupt the heap via n…CVE-2005-3624Libextractor · 2.3% likely

   CWE-189

5. Unspecified vulnerability in certain versions of xpdf after 3.00, as used in various products including (a) pdfkit.framework, (b) gpdf, (c) pdftohtml, and (d) libextractor, has un…CVE-2006-1244Libextractor · 2.2% likely

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.