CVE-2024-45043: fallo de gravedad media en open-telemetry opentelemetry-collector-contrib
OpenTelemetry Collector AWS Firehose Receiver Authentication Bypass Vulnerability
Publicada el
Seguir esta CVE+ Monitorear opentelemetry-collector-contrib+ Monitorear github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awsfirehosereceiver
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
13Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 5.3epss 0.5%
The OpenTelemetry Collector module AWS firehose receiver is for ingesting AWS Kinesis Data Firehose delivery stream messages and parsing the records received based on the configured record type. `awsfirehosereceiver` allows unauthenticated remote requests, even when configured to require a key. OpenTelemetry Collector can be configured to receive CloudWatch metrics via an AWS Firehose Stream. Firehose sets the header `X-Amz-Firehose-Access-Key` with an arbitrary configured string. The OpenTelemetry Collector awsfirehosereceiver can optionally be configured to require this key on incoming requests. However, when this is configured it **still accepts incoming requests with no key**. Only OpenTelemetry Collector users configured with the “alpha” `awsfirehosereceiver` module are affected. This module was added in version v0.49.0 of the “Contrib” distribution (or may be included in custom builds). There is a risk of unauthorized users writing metrics. Carefully crafted metrics could hide other malicious activity. There is no risk of exfiltrating data. It’s likely these endpoints will be exposed to the public internet, as Firehose does not support private HTTP endpoints. A fix was introduced in PR #34847 and released with v0.108.0. All users are advised to upgrade. There are no known workarounds for this vulnerability.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Productos afectados
open-telemetry · opentelemetry-collector-contribCVEs relacionadas — open-telemetry opentelemetry-collector-contrib
En el mismo producto, de las más peligrosas a las menos.
CVE-2026-55701MEDIUMOpenTelemetry githubreceiver silently ignores configured required_headers authenticationEPSS 0.7%CVE-2024-42368MEDIUMopen-telemetry has an Observable Timing DiscrepancyEPSS 0.6%CVE-2026-47256MEDIUMOpenTelemetry: Path traversal in Sentry exporter via attacker-controlled service.name reaches privileged Sentry API endpoints with operator bearer tokenEPSS 0.4%CVE-2026-42602HIGHazureauthextension Authenticate method does not validate bearer tokens, allowing auth bypass via replayEPSS 0.2%
Referencias
https://docs.aws.amazon.com/firehose/latest/dev/controlling-access.html#using-iam-httphttps://docs.aws.amazon.com/firehose/latest/dev/httpdeliveryrequestresponse.htmlhttps://github.com/open-telemetry/opentelemetry-collector#alphahttps://github.com/open-telemetry/opentelemetry-collector-contrib/pull/34847https://github.com/open-telemetry/opentelemetry-collector-contrib/security/advisories/GHSA-prf6-xjxh-p698https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/awsfirehosereceiverhttps://github.com/open-telemetry/opentelemetry-collector-releases/pull/74https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.108.0https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib