Google Go up to 1.13.12/1.14.4 X.509 Certificate Verification Certificate.Verify certificate validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Google Go up to 1.13.12/1.14.4 and classified as critical. This affects the function Certificate.Verify of the component X.509 Certificate Verification. This manipulation causes certificate validation.
The identification of this vulnerability is CVE-2020-14039. It is possible to initiate the attack remotely. There is no exploit available.
The affected component should be upgraded.
Details
A vulnerability was found in Google Go up to 1.13.12/1.14.4 (Programming Language Software). It has been declared as critical. Affected by this vulnerability is the function Certificate.Verify of the component X.509 Certificate Verification. The manipulation with an unknown input leads to a certificate validation vulnerability. The CWE definition for the vulnerability is CWE-295. The product does not validate, or incorrectly validates, a certificate. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In Go before 1.13.13 and 1.14.x before 1.14.5, Certificate.Verify may lack a check on the VerifyOptions.KeyUsages EKU requirements (if VerifyOptions.Roots equals nil and the installation is on Windows). Thus, X.509 certificate verification is incomplete.
The weakness was shared 07/17/2020 (Website). The advisory is shared at groups.google.com. This vulnerability is known as CVE-2020-14039 since 06/12/2020. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1587.003 for this issue.
Upgrading to version 1.13.13 or 1.14.5 eliminates this vulnerability.
The entry VDB-158751 is related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 1.13.0
- 1.13.1
- 1.13.2
- 1.13.3
- 1.13.4
- 1.13.5
- 1.13.6
- 1.13.7
- 1.13.8
- 1.13.9
- 1.13.10
- 1.13.11
- 1.13.12
- 1.14.0
- 1.14.1
- 1.14.2
- 1.14.3
- 1.14.4
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Certificate validationCWE: CWE-295 / CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Go 1.13.13/1.14.5
Timeline
06/12/2020 🔍07/17/2020 🔍
07/18/2020 🔍
11/04/2020 🔍
Sources
Vendor: google.comAdvisory: groups.google.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-14039 (🔍)
GCVE (CVE): GCVE-0-2020-14039
GCVE (VulDB): GCVE-100-158749
See also: 🔍
Entry
Created: 07/18/2020 08:52Updated: 11/04/2020 14:44
Changes: 07/18/2020 08:52 (42), 07/18/2020 08:57 (18), 11/04/2020 14:44 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.