Vendor Gnu


The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Type »

The moderation team is working with the threat intelligence team to categorize software that is affected by security vulnerabilities. This helps to illustrate the assignment of these categories to determine the most affected software types.

Product »

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation »

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability »

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector »

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication »

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction »

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index »

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base »

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp »

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB »

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.


The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

Vendor »

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research »

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day »

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today »

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume »

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities »

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Products (124): Anubis (2), Aspell (2), Automake (1), Bash (18), Binutils (15), Bison (4), C Library (128), Cfengine (4), Chess (3), Classpath (1), Coreutils (6), Data Display Debugger (1), Debugger (1), Ed (2), Emacs (17), Enscript (4), Escript (1), Fileutils (1), Flash Player (1), Flim (1), FreeRADIUS (12), FriBidi (1), GDB (2), GIMP (6), GMP (1), GNATS (1), GNUMP3D (3), GNU screen (1), GPGME (1), GRUB (2), Ghostscript (1), Gimp (1), Global (1), Gnash (2), GnuTLS (10), Gnumeric (1), Gnump3d (2), Groff (2), Grub 2 (1), Grub Legacy (1), Guile (2), Guix (1), Inkscape (1), Libextractor (13), Libidn2 (2), LibreDWG (35), Libtasn1 (7), Libtool (1), LimeWire (1), MPFR (1), MPlayer (7), Mailman (34), Mailutils (7), Midnight Commander (2), Openswan (3), PSPP (8), Parallel (2), Patch (14), Privacy Guard (3), Queue (1), Radius (4), Recutils (10), Rush (1), Samba (17), Screen (1), Serveez (1), Tar (1), WildFly (2), a2ps (3), adns (1), bash (1), binutils (173), cfengine (2), cflow (2), coreutils (3), cpio (4), ed (2), elfutils (4), emacs (2), findutils (2), finger (1), fingerd (2), gcc (10), gdb (3), gettext (2), gimp (2), glibc (2), gnash (1), gnubiff (3), gnuedu (1), gnump3d (1), gnutls (13), grep (2), groff (7), gv (2), gzip (7), ibackup (1), less (2), libcdio (3), libiberty (7), libidn (4), libmicrohttpd (2), libpng (4), libtasn1 (1), libtool (1), libtool-ltdl (1), lsh (1), lsh Daemon (1), m4 (2), mailutils (1), make (1), nano (2), oSIP (4), patch (1), phpBook (3), readline (1), screen (9), sharutils (5), tar (11), texinfo (2), tramp (1), userv (1), wget (20), zlib (3)

Link to Vendor Website:

02/27/20214.34.3GNU C Library Mutlibyte iconv infinite loopSoftware LibraryNot DefinedNot Defined0.09CVE-2020-27618
02/25/20213.93.9GNU C Library nscd netgroupcache.c double freeSoftware LibraryNot DefinedNot Defined0.05CVE-2021-27645
02/10/20217.07.0GNU Screen UTF-8 Encoding encoding.c denial of serviceUnknownNot DefinedNot Defined0.00CVE-2021-26937
01/28/20215.95.9GNU C Library ISO-2022-JP-3 Encoding denial of serviceSoftware LibraryNot DefinedOfficial Fix0.04CVE-2021-3326
01/05/20215.55.5GNU C Library iconv encoding errorSoftware LibraryNot DefinedOfficial Fix0.06CVE-2019-25013
01/05/20214.34.3GNU Binutils pef.c bfd_pef_parse_function_stubs null pointer dereferenceProgramming Tool SoftwareNot DefinedOfficial Fix0.05CVE-2020-35507
01/05/20214.34.3GNU Binutils pef.c bfd_pef_scan_start_address null pointer dereferenceProgramming Tool SoftwareNot DefinedOfficial Fix0.06CVE-2020-35496
01/05/20214.34.3GNU Binutils objdump pef.c null pointer dereferenceProgramming Tool SoftwareNot DefinedOfficial Fix0.07CVE-2020-35495
01/05/20216.36.3GNU Binutils tic4x-dis.c uninitialized resourceProgramming Tool SoftwareNot DefinedOfficial Fix0.06CVE-2020-35494
01/05/20216.36.3GNU Binutils PEF File Parser pef.c out-of-bounds readProgramming Tool SoftwareNot DefinedOfficial Fix0.06CVE-2020-35493
12/27/20205.55.5GNU Binutils libbfd.c bfd_getl_signed_32 heap-based overflowProgramming Tool SoftwareNot DefinedOfficial Fix0.05CVE-2020-35448
12/10/20205.05.0GNU Binutils _bfd_elf_get_symbol_version_string null pointer dereferenceProgramming Tool SoftwareNot DefinedOfficial Fix0.04CVE-2020-16599
12/10/20204.54.5GNU Binutils debug_get_real_type null pointer dereferenceProgramming Tool SoftwareNot DefinedOfficial Fix0.05CVE-2020-16598
12/10/20204.54.5GNU Binutils scan_unit_for_symbols denial of serviceProgramming Tool SoftwareNot DefinedOfficial Fix0.00CVE-2020-16593
12/10/20205.55.5GNU Binutils bfd_hash_lookup use after freeProgramming Tool SoftwareNot DefinedOfficial Fix0.04CVE-2020-16592
12/10/20204.54.5GNU Binutils process_symbol_table denial of serviceProgramming Tool SoftwareNot DefinedOfficial Fix0.05CVE-2020-16591
12/10/20205.55.5GNU Binutils File Descriptor process_symbol_table double freeProgramming Tool SoftwareNot DefinedOfficial Fix0.06CVE-2020-16590
12/06/20206.56.2GNU C Library ldbl2mpn.c sprintf stack-based overflowSoftware LibraryNot DefinedOfficial Fix0.04CVE-2020-29573
12/04/20205.55.5GNU C Library UCS4 Text denial of serviceSoftware LibraryNot DefinedNot Defined0.06CVE-2020-29562
10/06/20207.67.6GNU C Library search.texi return valueSoftware LibraryNot DefinedOfficial Fix0.00CVE-1999-0199
09/04/20205.45.4GNU Bison parse-gram.c input validationUnknownNot DefinedNot Defined0.00CVE-2020-24980
09/04/20205.45.4GNU Bison symtab.c out-of-bounds writeUnknownNot DefinedNot Defined0.06CVE-2020-24979
08/25/20204.44.4GNU Bison use after freeUnknownNot DefinedNot Defined0.06CVE-2020-24240
07/17/20205.45.1GNU LibreDWG null pointer dereferenceImage Processing SoftwareNot DefinedOfficial Fix0.05CVE-2020-15807
07/16/20207.27.2GNU LibreDWG bits.c bit_write_TF out-of-bounds readUnknownNot DefinedNot Defined0.05CVE-2019-20915

Do you want to use VulDB in your project?

Use the official API to access entries easily!