Repository navigation
[GHSA-q7rr-3cgh-j5r3] Prometheus exporter process crash via malformed HTTP request - #10226
Conversation
|
Hi there @pichlermarc! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository. This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory |
pichlermarc
left a comment
There was a problem hiding this comment.
Thanks for the update! I double-checked that and both updates are accurate:
@opentelemetry/sdk-node:
- not there in 0.56: https://github.com/open-telemetry/opentelemetry-js/blob/85dcbc7c55f002837f1bf1bf01145dbb34a55b40/experimental/packages/opentelemetry-sdk-node/package.json#L47-L62
- there in 0.57: https://github.com/open-telemetry/opentelemetry-js/blob/616d27a0a111c9b813d14c56d8d8f1ffbd7d7156/experimental/packages/opentelemetry-sdk-node/package.json#L55
@opentelemetry/auto-instrumentations-node:
- not there in 0.54.0 since
@opentelemetry/sdk-node@^0.56.0limits to@opentelemetry/sdk-node@~0.56.0: https://github.com/open-telemetry/opentelemetry-js-contrib/blob/auto-instrumentations-node-v0.54.0/metapackages/auto-instrumentations-node/package.json#L95 - there in 0.55.0 through
@opentelemetry/sdk-node@^0.57.0: https://github.com/open-telemetry/opentelemetry-js-contrib/blob/3ef5205e5353010184c69ff7b9f0f4830f0932de/metapackages/auto-instrumentations-node/package.json#L95
d10a69b
into
aaron-belenky/advisory-improvement-10226
|
Hi @aaron-belenky! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future! |
Updates
Comments
The two packages that need to change the affected range are marked as vulnerable because they depend on the vulnerable exporter-prometheus and pin the version to a vulnerable version.
sdk-node started to depend on exporter-prometheus in 0.57.0 - earlier versions don't use this dependency.
auto-instrumentations-node started to depend on a vulnerable version of sdk-node in 0.55.0 - earlier versions use versions before 0.57.0 of sdk-node.