Read the docs
TI-2020-20044 Aliases CVE-2020-37280GHSA-fpg7-639f-4v49

Memory exhaustion in cbor-sync via unchecked CBOR array lengths

Priority MEDIUM 44CWE-789Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · High
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-789.

Summary

cbor-sync through 1.0.4 from PelionIoT contains a resource exhaustion flaw in CBOR.decode, which trusts declared array and map lengths without checking the remaining input. A remote attacker can send a tiny crafted CBOR payload that declares huge lengths, driving billions of iterations and exhausting CPU and process memory. The CVSS 4.0 vector rates the impact as high availability impact with no authentication or user interaction required.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00538 45th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
PelionIoTcbor-syncup to 1.0.4—No fix listedCNA
  • cbor-sync VendorPelionIoT Affected up to 1.0.4 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for cbor-sync.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Timeline

  1. 2026-10-12 Threatist record created from CVE-2020-37280
  2. 2026-10-13 Alias added: GHSA-fpg7-639f-4v49
  3. 2026-10-13 Priority changed: MEDIUM → LOW
  4. 2026-10-13 CISA SSVC decision points changed
  5. 2026-10-13 Priority changed: LOW → MEDIUM

References

Sources