DELO-6300: fix dependency security vulnerabilities#233
Open
ikrascloudinary wants to merge 1 commit into
Open
Conversation
Bump the OpenTelemetry package set to the 0.220.0 (experimental) / 2.9.0 (stable) line so the transitive @opentelemetry/core moves from 2.7.1 to 2.9.0 (>= 2.8.0), resolving unbounded resource allocation in the baggage extract() path (SNYK-JS-OPENTELEMETRYCORE-17373280, GHSA-8988-4f7v-96qf). The otel stable packages pin @opentelemetry/core to an exact version, so a lone resolution isn't safe — the whole set must move together. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Vulnerabilities resolved
extractfunction (SNYK-JS-OPENTELEMETRYCORE-17373280, GHSA-8988-4f7v-96qf)Dependencies updated
@opentelemetry/coreis transitive. The stable otel packages pin it to an exact version (all were2.7.1), so a loneresolutionsoverride would fight those pins — the whole set must move together. Bumped to the current 0.220.0 (experimental) / 2.9.0 (stable) line:@opentelemetry/exporter-prometheus: ^0.218.0 → ^0.220.0@opentelemetry/instrumentation: ^0.218.0 → ^0.220.0@opentelemetry/instrumentation-express: ^0.66.0 → ^0.68.0@opentelemetry/instrumentation-http: ^0.218.0 → ^0.220.0@opentelemetry/resources: ^2.7.1 → ^2.9.0@opentelemetry/sdk-node: ^0.218.0 → ^0.220.0@opentelemetry/sdk-trace-base: ^2.7.1 → ^2.9.0@opentelemetry/semantic-conventions: ^1.41.1 → ^1.43.0@opentelemetry/api: unchanged at ^1.9.1 (peer^1.3.0satisfied)After install, all 24 copies of
@opentelemetry/corededupe to2.9.0; none below 2.8.0.Code changes
instrumentation.jsalready uses the v2 API (resourceFromAttributes,NodeSDK, stableATTR_*fromsemantic-conventions), which is unchanged across 2.7 → 2.9.Resolutions
Package version
1.3.12→1.3.14(PATCH — security-only fix;1.3.13is taken by the DELO-6281 PR DELO-6281: fix dependency security vulnerabilities #232)Test results
npm testpassed — 13 passing, no hard crashes or module errors.node --require ./instrumentation.js), exercising the SDK start + Prometheus exporter registration.Test plan
npm testpassesnode --require ./instrumentation.js start.js(Prometheus exporter on :6060)