Google Go up to 1.15 Encoding XML Package encoding error
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Google Go up to 1.15. Affected is an unknown function of the component Encoding XML Package. Performing a manipulation results in encoding error. This vulnerability is cataloged as CVE-2020-29510. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to use the suggested workaround.
Details
A vulnerability was found in Google Go up to 1.15 (Programming Language Software). It has been classified as critical. This affects an unknown functionality of the component Encoding XML Package. The manipulation with an unknown input leads to a encoding error vulnerability. CWE is classifying the issue as CWE-172. The product does not properly encode or decode the data, resulting in unexpected values. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was shared 12/15/2020. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2020-29510. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/17/2020).
The best possible mitigation is suggested to be Workaround.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Encoding errorCWE: CWE-172
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: WorkaroundStatus: 🔍
0-Day Time: 🔍
Timeline
12/03/2020 🔍12/15/2020 🔍
12/15/2020 🔍
12/17/2020 🔍
Sources
Vendor: google.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2020-29510 (🔍)
GCVE (CVE): GCVE-0-2020-29510
GCVE (VulDB): GCVE-100-166209
Entry
Created: 12/15/2020 07:22Updated: 12/17/2020 13:04
Changes: 12/15/2020 07:22 (37), 12/17/2020 12:58 (5), 12/17/2020 13:04 (8)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.