protobuf up to 3.14.x Error Message null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in protobuf up to 3.14.x. Affected is an unknown function of the component Error Message Handler. Performing a manipulation results in null pointer dereference. This vulnerability is known as CVE-2021-22570. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in protobuf up to 3.14.x. This affects an unknown code of the component Error Message Handler. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability.
The weakness was published 01/26/2022. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2021-22570 since 01/05/2021. Neither technical details nor an exploit are publicly available.
Upgrading to version 3.15.0 eliminates this vulnerability. The upgrade is hosted for download at github.com.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (Google Inc.): 🔍
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: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
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: protobuf 3.15.0
Timeline
01/05/2021 🔍01/26/2022 🔍
01/26/2022 🔍
01/29/2022 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2021-22570 (🔍)
GCVE (CVE): GCVE-0-2021-22570
GCVE (VulDB): GCVE-100-191685
Entry
Created: 01/26/2022 22:56Updated: 01/29/2022 09:49
Changes: 01/26/2022 22:56 (49), 01/29/2022 09:47 (1), 01/29/2022 09:49 (1)
Complete: 🔍
Cache ID: 216:0E0: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.