ZeroMQ Server up to 4.3.2 Decoder decoder_allocators.hpp out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in ZeroMQ Server up to 4.3.2 and classified as critical. The impacted element is an unknown function of the file src/decoder_allocators.hpp of the component Decoder. The manipulation leads to out-of-bounds write. This vulnerability is documented as CVE-2021-20235. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability, which was classified as critical, has been found in ZeroMQ Server up to 4.3.2. This issue affects an unknown part of the file src/decoder_allocators.hpp of the component Decoder. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. Using CWE to declare the problem leads to CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability.
The weakness was released 04/02/2021. It is possible to read the advisory at bugzilla.redhat.com. The identification of this vulnerability is CVE-2021-20235. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 4.3.3 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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: 🔍
Exploiting
Class: Out-of-bounds writeCWE: CWE-787 / CWE-119
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: Server 4.3.3
Timeline
12/17/2020 🔍04/02/2021 🔍
04/02/2021 🔍
04/07/2021 🔍
Sources
Advisory: bugzilla.redhat.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2021-20235 (🔍)
GCVE (CVE): GCVE-0-2021-20235
GCVE (VulDB): GCVE-100-172091
Entry
Created: 04/02/2021 08:07Updated: 04/07/2021 18:32
Changes: 04/02/2021 08:07 (40), 04/07/2021 18:32 (5)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.