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 (104): actix-codec Crate, actix-http Crate, actix-service Crate, actix-utils Crate, alpm-rs Crate, ammonia Crate, arc-swap Crate, array-queue Crate, arrayfire Crate, arr Crate, asn1_der Crate, async-h1, atom Crate, bigint Crate, bitvec Crate, blake2 Crate, branca Crate, bumpalo Crate, cbox Crate, chacha20 Crate, chttp Crate, claxon Crate, compact_arena Crate, concread Crate, cookie Crate, crayon Crate, crossbeam-channel Crate, crossbeam Crate, dync Crate, failure Crate, flatbuffers Crate, futures-intrusive Crate, futures-task Crate, futures-util Crate, Generator Crate, http crate, Hyper Crate, hyper Crate, Image Crate, internment 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, memoffset Crate, miow Crate, mio Crate, mozwire Crate, multihash Crate, nanorand Crate, ncurses Crate, net2 Crate, obstack Crate, once_cell Crate, ordered-float crate, ordnung Crate, orion Crate, os_str_bytes Crate, ozone Crate, pancurses Crate, portaudio-rs Crate, portaudio Crate, prost Crate, protobuf Crate, pyo3 Crate, rand_core crate, renderdoc Crate, rgb crate, rio crate, rocket Crate, rulinalg Crate, rusqlite Crate, rustls Crate, safe-transmute 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, stack Crate, streebog Crate, string-interner Crate, tar Crate, thex Crate, Time Crate, tiny_http Crate, tokio-rustls Crate, traitobject Crate, trust-dns-proto Crate, trust-dns-server Crate, try-mutex Crate, untrusted Crate, ws Crate, yaml-rust Crate

12/31/20205.55.5concread Crate unknown vulnerabilityconcread CrateNot DefinedOfficial Fix0.05CVE-2020-35928
12/31/20205.55.5thex Crate Thread unknown vulnerabilitythex CrateNot DefinedNot Defined0.06CVE-2020-35927
12/31/20203.53.5nanorand Crate entropynanorand CrateNot DefinedOfficial Fix0.06CVE-2020-35926
12/31/20205.55.5magnetic Crate Thread MPMCProducer memory corruptionmagnetic CrateNot DefinedOfficial Fix0.05CVE-2020-35925
12/31/20205.55.5try-mutex Crate Thread unknown vulnerabilitytry-mutex CrateNot DefinedOfficial Fix0.00CVE-2020-35924
12/31/20205.55.5ordered-float crate unknown vulnerabilityordered-float crateNot DefinedOfficial Fix0.00CVE-2020-35923
12/31/20205.55.5mio Crate SocketAddr memory corruptionmio CrateNot DefinedOfficial Fix0.06CVE-2020-35922
12/31/20205.55.5miow Crate SocketAddr memory corruptionmiow CrateNot DefinedOfficial Fix0.00CVE-2020-35921
12/31/20205.55.5socket2 Crate SocketAddr memory corruptionsocket2 CrateNot DefinedOfficial Fix0.00CVE-2020-35920
12/31/20205.55.5net2 Crate SocketAddr memory corruptionnet2 CrateNot DefinedOfficial Fix0.00CVE-2020-35919
12/31/20203.53.5branca Crate Token Decoding denial of servicebranca CrateNot DefinedOfficial Fix0.06CVE-2020-35918
12/31/20205.55.5pyo3 Crate use after freepyo3 CrateNot DefinedOfficial Fix0.06CVE-2020-35917
12/31/20205.55.5Image Crate unknown vulnerabilityImage CrateNot DefinedOfficial Fix0.06CVE-2020-35916
12/31/20205.55.5futures-intrusive Crate Thread GenericMutexGuard unknown vulnerabilityfutures-intrusive CrateNot DefinedOfficial Fix0.04CVE-2020-35915
12/31/20205.55.5lock_api Crate RwLockWriteGuard unknown vulnerabilitylock_api CrateNot DefinedOfficial Fix0.00CVE-2020-35914
12/31/20205.55.5lock_api Crate RwLockReadGuard unknown vulnerabilitylock_api CrateNot DefinedOfficial Fix0.06CVE-2020-35913
12/31/20205.55.5lock_api Crate MappedRwLockWriteGuard unknown vulnerabilitylock_api CrateNot DefinedOfficial Fix0.00CVE-2020-35912
12/31/20205.55.5lock_api Crate MappedRwLockReadGuard unknown vulnerabilitylock_api CrateNot DefinedOfficial Fix0.00CVE-2020-35911
12/31/20205.55.3lock_api Crate unknown vulnerabilitylock_api CrateNot DefinedOfficial Fix0.12CVE-2020-35910
12/31/20203.53.5multihash Crate from_slice denial of servicemultihash CrateNot DefinedOfficial Fix0.00CVE-2020-35909
12/31/20205.55.5futures-util Crate FuturesUnordered unknown vulnerabilityfutures-util CrateNot DefinedOfficial Fix0.05CVE-2020-35908
12/31/20203.53.5futures-task Crate noop_waker_ref null pointer dereferencefutures-task CrateNot DefinedOfficial Fix0.25CVE-2020-35907
12/31/20205.55.5futures-task Crate waker use after freefutures-task CrateNot DefinedOfficial Fix0.12CVE-2020-35906
12/31/20205.55.5futures-util Crate map race conditionfutures-util CrateNot DefinedOfficial Fix0.05CVE-2020-35905
12/31/20205.55.5crossbeam-channel Crate memory corruptioncrossbeam-channel CrateNot DefinedOfficial Fix0.45CVE-2020-35904

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!