Home/CVE/The OpenTelemetry Collector offers a vendor-agnostic implementation on how to receive, process and export telemetry data
CVE

CVE-2024-36129

The OpenTelemetry Collector offers a vendor-agnostic implementation on how to receive, process and export telemetry data

The OpenTelemetry Collector offers a vendor-agnostic implementation on how to receive, process and export telemetry data. An unsafe decompression vulnerability allows unauthenticated attackers to crash the collector via excessive memory consumption. OTel Collector version 0.102.1 fixes this issue.

It is also fixed in the confighttp module version 0.102.0 and configgrpc module version 0.102.1.

HIGH · CVSS 8.2 EPSS 0.02397
Act now
  • Public exploit or PoC is available
  • SSVC automatable: yes - attacks can be scripted at scale
  • CVSS base score ≥ 7.0
Sigma rules0 YARA rules0
⬡

Weakness Classification

CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer
CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer
▤

Affected Products & Versions

3
opentelemetry configgrpc< 0.102.1
opentelemetry confighttp< 0.102.0
opentelemetry collector< 0.102.1
▤

Affected Packages

2
Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Go go.opentelemetry.io/collector/config/configgrpc HIGH fixed in 0.102.1
Go go.opentelemetry.io/collector/config/confighttp HIGH fixed in 0.102.0
⚠

Public Exploits & PoCs

1
pocgithub.com · GHSA-c74f-6mfw-mm4vgithub.com
▣

Scoring & Timeline

8.2
HIGH · CVSS v3.1 · security-advisories@github.com
View on NVD
Attack Vector
Network Adjacent Local Physical
Attack Complexity
Low High
Privileges Required
None Low High
User Interaction
None Required
Scope
Unchanged Changed
Confidentiality
None Low High
Integrity
None Low High
Availability
None Low High
Published to NVD05 Jun 2024 · 06:15 PM
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
SSVC triage · cisa-vulnrichment
Exploitation
poc
Automatable
yes
Technical impact
partial
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
⚑

Vendor Advisories

2
suse-csafopenSUSE-SU-2024:14439-1
rhsaRHSA-2024:3943Important
🔗

References & Sources

3
Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
https://github.com/open-telemetry/opentelemetry-collector/pull/10289Patch
https://github.com/open-telemetry/opentelemetry-collector/pull/10323Patch
https://opentelemetry.io/blog/2024/cve-2024-36129Vendor Advisory
Intelligence Graph · click any node to traverse
CVETechnique ActorTool Family
drag to reposition · click any node to traverse · button top-right enlarges
External lookups - second-class, for what we don’t hold ourselves
NVDCVE.orgCISAVulnersExploit-DBGitHub PoCVulnCheck KEVGreyNoise
Vulnerabilities
CISA KEV catalog
CWE weaknesses
CAPEC attack patterns
Package vulnerabilities
Threat intelligence
Threat actors
Tools & malware
ATT&CK techniques
IOCs
Detection & defense
Sigma rules
YARA rules
Atomic Red Team tests
D3FEND countermeasures
Compliance
NIST 800-53
ISO 27001:2022
SOC 2 TSC
PCI-DSS v4.0
CIS Controls v8.1
About
All capabilities
Live statistics
Data sources
Privacy policy
Terms of service
threatengine.sh  ·  Open-source threat intelligence platform  ·  100+ authoritative sources  ·  Every fact traces to its origin