turkdevops / grafana

The tool for beautiful monitoring and metric analytics & dashboards for Graphite, InfluxDB & Prometheus & More
https://grafana.com
Apache License 2.0
1 stars 0 forks source link

CVE-2020-7919 (High) detected in github.com/golang/crypto-c7e5f84aec591254278750bee18f39e5dd19cdb5 - autoclosed #623

Closed mend-bolt-for-github[bot] closed 2 years ago

mend-bolt-for-github[bot] commented 2 years ago

CVE-2020-7919 - High Severity Vulnerability

Vulnerable Library - github.com/golang/crypto-c7e5f84aec591254278750bee18f39e5dd19cdb5

[mirror] Go supplementary cryptography libraries

Dependency Hierarchy: - :x: **github.com/golang/crypto-c7e5f84aec591254278750bee18f39e5dd19cdb5** (Vulnerable Library)

Found in HEAD commit: 3b956fc649fb80f3c2734d2976b6fce921c134b7

Found in base branch: datasource-meta

Vulnerability Details

Go before 1.12.16 and 1.13.x before 1.13.7 (and the crypto/cryptobyte package before 0.0.0-20200124225646-8b5121be2f68 for Go) allows attacks on clients (resulting in a panic) via a malformed X.509 certificate.

Publish Date: 2020-03-16

URL: CVE-2020-7919

CVSS 3 Score Details (7.5)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7919

Release Date: 2020-03-16

Fix Resolution: go - 1.12.16,1.13.7;crypto - v0.0.0-20200128174031-69ecbb4d6d5d


Step up your Open Source Security Game with WhiteSource here

mend-bolt-for-github[bot] commented 2 years ago

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #641

mend-bolt-for-github[bot] commented 2 years ago

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #641