Type Rust Package


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.

Vendor »

Identifying all affected vendors is a good starting point for an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

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 (163): abi_stable Crate, actix-codec Crate, actix-http Crate, actix-service Crate, actix-utils Crate, adtensor Crate, alpm-rs Crate, ammonia Crate, aovec Crate, arc-swap Crate, arenavec Crate, array-queue Crate, arrayfire Crate, arr Crate, asn1_der Crate, async-h1, async-h1 Crate, atomic-option Crate, atom Crate, autorand Crate, av-data Crate, bam Crate, basic_dsp_matrix Crate, bigint Crate, bitvec Crate, blake2 Crate, branca Crate, bra Crate, bumpalo Crate, buttplug Crate, byte_struct Crate, cache Crate, calamine Crate, cbox Crate, cdr Crate, chacha20 Crate, chttp Crate, claxon Crate, compact_arena Crate, comrak Crate, concread Crate, conquer-once Crate, containers Crate, cookie Crate, crayon Crate, crossbeam-channel Crate, crossbeam Crate, diesel Crate, dync Crate, endian_trait Crate, eventio Crate, failure Crate, fil-ocl Crate, flatbuffers Crate, fltk Crate, futures-intrusive Crate, futures-task Crate, futures-util Crate, Generator Crate, gfwx Crate, glsl-layout Crate, hashconsing Crate, http crate, Hyper Crate, hyper Crate, id-map Crate, Image Crate, im Crate, insert_many Crate, internment Crate, late-static Crate, lazy-init Crate, libflate Crate, libp2p-core Crate, libpulse-binding Crate, libsecp256k1 Crate, linea Crate, linked-hash-map, lock_api Crate, lucet-runtime-internals Crate, magnetic Crate, marc Crate, may_queue Crate, memoffset Crate, miow Crate, mio Crate, mozwire Crate, ms3d Crate, multihash Crate, multiqueue2 Crate, nanorand Crate, nano_arena Crate, nb-connect Crate, ncurses Crate, net2 Crate, obstack Crate, once_cell Crate, ordered-float crate, ordnung Crate, orion Crate, os_str_bytes Crate, outer_cgi Crate, ozone Crate, pancurses Crate, parse_duration Crate, portaudio-rs Crate, portaudio Crate, postscript Crate, prost Crate, protobuf Crate, pyo3 Crate, quinn Crate, qwutils Crate, rand_core Crate, rand_core crate, raw-cpuid Crate, reffers Crate, renderdoc Crate, reorder Crate, rgb crate, rio crate, rocket Crate, rulinalg Crate, rusb Crate, rusqlite Crate, rustls Crate, safe-transmute Crate, scratchpad Crate, security-framework Crate, serde_cbor Crate, simd-json Crate, simple-slab Crate, sized-chunks crate, slice-deque Crate, smallvec Crate, socket2 Crate, sodiumoxide Crate, Spin Crate, stackvector Crate, stack Crate, stack_dst Crate, streebog Crate, string-interner Crate, tar Crate, telemetry Crate, thex Crate, through Crate, Time Crate, tiny_http Crate, tokio-rustls Crate, toodee Crate, traitobject Crate, truetype Crate, trust-dns-proto Crate, trust-dns-server Crate, try-mutex Crate, untrusted Crate, uu_od Crate, va-ts Crate, ws Crate, xcb Crate, yaml-rust Crate, yottadb Crate

04/08/20215.55.5id-map Crate remove_set double freeid-map CrateNot DefinedNot Defined1.59-CVE-2021-30457
04/08/20215.55.5id-map Crate get_or_insert double freeid-map CrateNot DefinedNot Defined1.68-CVE-2021-30456
04/08/20215.55.5id-map Crate Clone clone clone_from double freeid-map CrateNot DefinedNot Defined2.11-CVE-2021-30455
04/08/20215.55.5outer_cgi Crate KeyValueReader uninitialized pointerouter_cgi CrateNot DefinedOfficial Fix2.07-CVE-2021-30454
04/01/20215.55.5reorder Crate swap_index uninitialized pointerreorder CrateNot DefinedNot Defined0.39CVE-2021-29942
04/01/20215.55.5reorder Crate swap_index out-of-bounds writereorder CrateNot DefinedNot Defined0.34CVE-2021-29941
04/01/20213.53.5through Crate through_and double freethrough CrateNot DefinedNot Defined0.56CVE-2021-29940
04/01/20215.55.5stackvector Crate extend out-of-bounds writestackvector CrateNot DefinedNot Defined0.39CVE-2021-29939
04/01/20213.53.5slice-deque Crate Predicate drain_filter denial of serviceslice-deque CrateNot DefinedNot Defined0.34CVE-2021-29938
04/01/20215.55.5telemetry Crate vec_with_size uninitialized pointertelemetry CrateNot DefinedNot Defined0.43CVE-2021-29937
04/01/20215.55.5adtensor Crate FromIterator uninitialized pointeradtensor CrateNot DefinedNot Defined1.04CVE-2021-29936
04/01/20213.53.4rocket Crate Formatter use after freerocket CrateNot DefinedOfficial Fix0.89CVE-2021-29935
04/01/20213.53.4uu_od Crate PartialReader uninitialized pointeruu_od CrateNot DefinedOfficial Fix1.00CVE-2021-29934
04/01/20213.53.5insert_many Crate a .next denial of serviceinsert_many CrateNot DefinedNot Defined0.85CVE-2021-29933
04/01/20215.55.5parse_duration Crate Exponent memory allocationparse_duration CrateNot DefinedNot Defined1.11CVE-2021-29932
04/01/20213.53.5arenavec Crate drop denial of servicearenavec CrateNot DefinedNot Defined1.12CVE-2021-29931
04/01/20213.53.5arenavec Crate default uninitialized pointerarenavec CrateNot DefinedNot Defined0.91CVE-2021-29930
04/01/20216.56.5endian_trait Crate double freeendian_trait CrateNot DefinedNot Defined2.95CVE-2021-29929
03/12/20217.37.0fltk Crate Constructor out-of-bounds readfltk CrateNot DefinedOfficial Fix0.04CVE-2021-28308
03/12/20215.55.3fltk Crate Window Icon null pointer dereferencefltk CrateNot DefinedOfficial Fix0.90CVE-2021-28307
03/12/20215.55.3fltk Crate Image null pointer dereferencefltk CrateNot DefinedOfficial Fix0.04CVE-2021-28306
03/12/20217.67.3diesel Crate SQLite Backend sqlite3_column_name use after freediesel CrateNot DefinedOfficial Fix0.04CVE-2021-28305
03/05/20217.67.3internment Crate memory corruptioninternment CrateNot DefinedOfficial Fix0.04CVE-2021-28037
03/05/20216.56.2quinn Crate SocketAddrV6 memory corruptionquinn CrateNot DefinedOfficial Fix0.12CVE-2021-28036
03/05/20217.67.3stack_dst Crate push_inner uninitialized pointerstack_dst CrateNot DefinedOfficial Fix0.00CVE-2021-28035

Do you want to use VulDB in your project?

Use the official API to access entries easily!