[GHSA-8988-4f7v-96qf] OpenTelemetry Core: Unbounded memory allocation in W3C Baggage propagation#8474
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 |
There was a problem hiding this comment.
Pull request overview
This PR updates a GitHub-reviewed advisory entry for GHSA-8988-4f7v-96qf / CVE-2026-54285 (OpenTelemetry Core baggage propagation) to reflect a CVSS v3 change and updates the advisory’s modified timestamp.
Changes:
- Updates the advisory
modifiedtimestamp. - Changes the CVSS v3.1 vector string in the
severitysection.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| { | ||
| "type": "CVSS_V3", | ||
| "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L" | ||
| "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L" |
|
Hi @Lokeninfinitypoint - can you elaborate why the attack vector should be changed to Local? As the copilot review already stated, HTTP headers that can trigger this originate from the network (for example through an HTTP request). |
Updates
Comments
change imporvment