cbor-sync through 1.0.4 Memory Exhaustion via Unchecked CBOR Array Lengths
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| PelionIoT | cbor-sync | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Pelioniot | Cbor-sync |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.538% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pelioniot
Pelioniot cbor-sync |
|
| Vendors & Products |
Pelioniot
Pelioniot cbor-sync |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | cbor-sync through 1.0.4 contains a resource exhaustion vulnerability in CBOR.decode that trusts declared array and map lengths without checking remaining input. Remote attackers can supply a tiny crafted CBOR payload declaring huge lengths to drive billions of iterations, exhausting CPU and process memory. | |
| Title | cbor-sync through 1.0.4 Memory Exhaustion via Unchecked CBOR Array Lengths | |
| Weaknesses | CWE-789 | |
| References |
| |
| Metrics |
cvssV3_1
|