wolfSSL wolfMQTT 1.9 MqttDecode_Publish heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in wolfSSL wolfMQTT 1.9. Affected is the function MqttDecode_Publish. This manipulation causes heap-based overflow.
The identification of this vulnerability is CVE-2021-45933. There is no exploit available.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in wolfSSL wolfMQTT 1.9. It has been declared as critical. Affected by this vulnerability is the function MqttDecode_Publish. The manipulation with an unknown input leads to a heap-based overflow vulnerability. The CWE definition for the vulnerability is CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was shared 01/01/2022. The advisory is shared at bugs.chromium.org. This vulnerability is known as CVE-2021-45933 since 12/31/2021. Technical details are known, but no exploit is available.
Applying the patch 84d4b53122e0fa0280c7872350b89d5777dabbb2 is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Product: https://github.com/wolfSSL/wolfMQTT/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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: Heap-based overflowCWE: CWE-122 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 84d4b53122e0fa0280c7872350b89d5777dabbb2
Timeline
12/31/2021 🔍01/01/2022 🔍
01/01/2022 🔍
01/05/2022 🔍
Sources
Product: github.comAdvisory: 84d4b53122e0fa0280c7872350b89d5777dabbb2
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2021-45933 (🔍)
GCVE (CVE): GCVE-0-2021-45933
GCVE (VulDB): GCVE-100-189529
Entry
Created: 01/01/2022 10:32Updated: 01/05/2022 13:48
Changes: 01/01/2022 10:32 (41), 01/05/2022 13:48 (2)
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.