High
cbor-sync through 1.0.4 Memory Exhaustion via Unchecked CBOR Array Lengths
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.
Announced Source revision 1
Original source ↗CVE-2020-37280
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2020-37280
cbor-sync
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"repo": "https://github.com/PelionIoT/cbor-sync",
"vendor": "PelionIoT",
"product": "cbor-sync",
"versions": [
{
"status": "affected",
"version": "0",
"versionType": "semver",
"lessThanOrEqual": "1.0.4"
}
],
"packageURL": "pkg:npm/cbor-sync",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2020-37280
Source reference:
/cveMetadata/cveId
Publisher severity
high
Source reference: /containers/cna/metrics
- Event
- #20443 · Revision 1
- Added to Heist Feed
- Publisher date