chore(deps): update dependency @opentelemetry/sdk-node to v0.217.0 [security]#1375
Conversation
|
@launchdarkly/js-sdk-common size report |
|
@launchdarkly/js-client-sdk size report |
|
@launchdarkly/js-client-sdk-common size report |
|
@launchdarkly/browser size report |
b33d00b to
100fe8f
Compare
f2ceaa3 to
aa211c4
Compare
aa211c4 to
d2bb5a7
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This PR contains the following updates:
0.49.1→0.217.0Prometheus exporter process crash via malformed HTTP request
CVE-2026-44902 / GHSA-q7rr-3cgh-j5r3
More information
Details
Summary
A single malformed HTTP request crashes any Node.js process running the OpenTelemetry JS Prometheus exporter. The metrics endpoint (default
0.0.0.0:9464) has no error handling around URL parsing, so a request with an invalid URI causes an uncaughtTypeErrorthat terminates the process.You are affected by this vulnerability if either of the following apply to your application:
@opentelemetry/exporter-prometheusin your code through its built-in server.OTEL_METRICS_EXPORTERenvironment variable includesprometheusAND@opentelemetry/sdk-node@opentelemetry/auto-instrumentations-nodevia--require @​opentelemetry/auto-instrumentations-node/register/--import @​opentelemetry/auto-instrumentations-node/registerImpact
Denial of service. Any application using the OpenTelemetry Prometheus exporter’s built-in server can be crashed by a single unauthenticated network packet sent to the metrics port. No authentication, special privileges, or prior access is required.
Remediation
Update to the fixed version
Update
@opentelemetry/exporter-prometheusand@opentelemetry/sdk-nodeto version 0.217.0 or later.Update
@opentelemetry/auto-instrumentations-nodeto version 0.75.0 or later.This release adds proper error handling around the URL constructor, returning an HTTP
400response on parse failure rather than allowing the exception to propagate and crash the process.Do Not Expose the Endpoint to Untrusted Users
If updating is not immediately feasible, restrict access to the metrics endpoint so that it is not reachable by untrusted or unauthenticated network clients. For example:
Bind to localhost only by setting the
hostoption to127.0.0.1when configuring thePrometheusExporter, so the port is not exposed on public or shared network interfacesUse a firewall or network policy to restrict access to port
9464(or whichever port you have configured) to only trusted Prometheus scrape hostsPlace the endpoint behind a reverse proxy that filters or validates incoming requests before they reach the exporter
Details
In
PrometheusExporter.ts, the_requestHandlercallsnew URL(request.url, this._baseUrl)without any error handling. Node's HTTP parser accepts absolute-form URIs (e.g.http://) for proxy compatibility, including malformed ones. Whenrequest.urlis"http://", theURLconstructor throwsTypeError: Invalid URL. Since there is no try-catch in the handler, the exception propagates as an uncaught exception and crashes the process.The Prometheus metrics endpoint is unauthenticated by design (Prometheus scrapes it) and binds to
0.0.0.0by default, meaning it is reachable by any network client that can connect to the metrics port.Proof of Concept
Start any Node.js application with the Prometheus exporter running on the default port
9464, then send a single raw TCP packet:The process crashes immediately with:
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
open-telemetry/opentelemetry-js (@opentelemetry/sdk-node)
v0.217.0Compare Source
v0.216.0Compare Source
v0.215.0Compare Source
v0.214.0Compare Source
v0.213.0Compare Source
v0.212.0Compare Source
v0.211.0Compare Source
v0.210.0Compare Source
v0.209.0Compare Source
v0.208.0Compare Source
v0.207.0Compare Source
v0.206.0Compare Source
v0.205.0Compare Source
v0.204.0Compare Source
v0.203.0Compare Source
v0.202.0Compare Source
v0.201.1Compare Source
v0.201.0Compare Source
v0.200.0Compare Source
v0.57.2Compare Source
v0.57.1Compare Source
v0.57.0Compare Source
v0.56.0Compare Source
v0.55.0Compare Source
v0.54.2Compare Source
v0.54.1Compare Source
v0.54.0Compare Source
v0.53.0Compare Source
v0.52.1Compare Source
v0.52.0Compare Source
v0.51.1Compare Source
v0.51.0Compare Source
v0.50.0Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.
Note
Medium Risk
Large OpenTelemetry version bumps can change SDK/runtime behavior and may subtly affect tracing initialization or test expectations, though the code changes are limited to dev/test configuration.
Overview
Updates OpenTelemetry dev dependencies in
@launchdarkly/node-server-sdk-otel(@opentelemetry/sdk-nodeto0.217.0and@opentelemetry/sdk-trace-nodeto2.7.1).Adjusts
TracingHook.test.tsto disableNodeSDKresource auto-detection (autoDetectResources: false) so spans are exported synchronously under the newerSimpleSpanProcessorbehavior.Reviewed by Cursor Bugbot for commit 10fa937. Bugbot is set up for automated code reviews on this repo. Configure here.