CVSSv3 April 2019info

Timeline

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.

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.

NVD »

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.

PublishedBaseVDBNVDVendResVulnerabilityCTICVE
04/30/20198.57.39.8
 
 
Crestron AM-100/AM-101 Web Interface hard-coded credentials0.04CVE-2019-3939
04/30/20196.55.37.8
 
 
Crestron AM-100/AM-101 Configuration File hard-coded credentials0.05CVE-2019-3938
04/30/20196.55.37.8
 
 
Crestron AM-100/AM-101 scfgdndf Credentials credentials management0.05CVE-2019-3937
04/30/20196.45.37.5
 
 
Crestron AM-100/AM-101 Service Port 389 input validation0.11CVE-2019-3936
04/30/20197.47.37.5
 
 
Crestron AM-100/AM-101 Slie Show conference.cgi improper authentication0.09CVE-2019-3935
04/30/20195.35.35.3
 
 
Crestron AM-100/AM-101 login.cgi access control0.06CVE-2019-3934
04/30/20195.35.35.3
 
 
Crestron AM-100/AM-101 browserslide.jpg access control0.06CVE-2019-3933
04/30/20198.57.39.8
 
 
Crestron AM-100/AM-101 return.tgi hard-coded credentials0.00CVE-2019-3932
04/30/20198.88.88.8
 
 
Crestron AM-100/AM-101 cURL return.cgi injection0.04CVE-2019-3931
04/30/20199.910.09.8
 
 
Crestron AM-100/AM-101 libAwgCgi.so PARSERtoCHAR memory corruption0.00CVE-2019-3930
04/30/20199.89.89.8
 
 
Crestron AM-100/AM-101 HTTP Endpoint file_transfer.cgi command injection0.09CVE-2019-3929
04/30/20196.37.35.3
 
 
Crestron AM-100/AM-101 SNMP information disclosure0.12CVE-2019-3928
04/30/20198.57.39.8
 
 
Crestron AM-100/AM-101 SNMP credentials management0.00CVE-2019-3927
04/30/20199.89.89.8
 
 
Crestron AM-100/AM-101 SNMP command injection0.08CVE-2019-3926
04/30/20199.89.89.8
 
 
Crestron AM-100/AM-101 SNMP command injection0.06CVE-2019-3925
04/30/20198.57.39.8
 
 
signing-party gpg-key2ps command injection0.06CVE-2019-11627
04/30/20195.35.35.3
 
 
doorGets ajaxRouter.php Path pathname traversal0.05CVE-2019-11626
04/30/20194.84.74.9
 
 
doorGets emailingRequest.php sql injection0.05CVE-2019-11625
04/30/20194.33.84.9
 
 
doorGets configurationRequest.php access control0.05CVE-2019-11624
04/30/20194.84.74.9
 
 
doorGets configurationRequest.php sql injection0.05CVE-2019-11623
04/30/20194.84.74.9
 
 
doorGets modulecategoryRequest.php sql injection0.07CVE-2019-11622
04/30/20194.84.74.9
 
 
doorGets configurationRequest.php sql injection0.00CVE-2019-11621
04/30/20194.84.74.9
 
 
doorGets modulecategoryRequest.php sql injection0.00CVE-2019-11620
04/30/20194.84.74.9
 
 
doorGets configurationRequest.php sql injection0.00CVE-2019-11619
04/30/20198.57.39.8
 
 
doorGets Access Token index.php credentials management0.04CVE-2019-11618
04/30/20197.05.38.8
 
 
doorGets configurationRequest.php cross-site request forgery0.05CVE-2019-11617
04/30/20197.55.39.8
 
 
doorGets admin.php Password credentials management0.00CVE-2019-11616
04/30/20197.56.38.8
 
 
doorGets File Upload upload.php unrestricted upload0.06CVE-2019-11615
04/30/20197.47.37.5
 
 
doorGets commentView.php sql injection0.05CVE-2019-11614
04/30/20196.46.36.5
 
 
doorGets contactView.php sql injection0.00CVE-2019-11613
04/30/20197.06.57.5
 
 
doorGets deletefile.php access control0.05CVE-2019-11612
04/30/20196.45.37.5
 
 
doorGets download.php information disclosure0.05CVE-2019-11611
04/30/20196.45.37.5
 
 
doorGets downloaddir.php information disclosure0.05CVE-2019-11610
04/30/20196.75.38.2
 
 
doorGets movefile.php information disclosure0.00CVE-2019-11609
04/30/20196.75.38.2
 
 
doorGets renamefile.php information disclosure0.00CVE-2019-11608
04/30/20196.45.37.5
 
 
doorGets copydir.php information disclosure0.00CVE-2019-11607
04/30/20196.45.37.5
 
 
doorGets copyfile.php information disclosure0.05CVE-2019-11606
04/30/20196.46.36.5
 
 
Apache Archiva Artifact Upload input validation0.04CVE-2019-0214
04/30/20196.46.36.5
 
 
Apache Archiva Artifact Upload input validation0.03CVE-2019-0213
04/30/20197.47.37.5
 
 
Apache Camel path traversal0.05CVE-2019-0194

Do you want to use VulDB in your project?

Use the official API to access entries easily!