Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

security update backport – CVE-2023-45142 #4447

Open
jufemaiz opened this issue Oct 18, 2023 · 1 comment
Open

security update backport – CVE-2023-45142 #4447

jufemaiz opened this issue Oct 18, 2023 · 1 comment
Labels
bug Something isn't working response needed Waiting on user input before progress can be made

Comments

@jufemaiz
Copy link

jufemaiz commented Oct 18, 2023

Description

CVE-2023-45142 notes that the affected versions are < 0.44.0, however v0.44.0 has breaking changes due to semconv changes for a number of packages in this repository.

Backporting the CVE fix to older releases is needed to maintain security while continuing to use specified otel semconv implementations.

Environment

  • go.opentelemetry.io/contrib version: < v0.44.0

Steps To Reproduce

N/A

Expected behavior

Secured releases of older pinned semconv in use for each of the packages.

Related

#4277

#3657

@jufemaiz jufemaiz added the bug Something isn't working label Oct 18, 2023
@pellared
Copy link
Member

pellared commented Oct 20, 2023

Backporting the CVE fix to older releases is needed to maintain security while continuing to use specified otel semconv implementations.

What version(s) do you have in mind?

Cannot you use any workarounds described in GHSA-rcjv-mgp8-qvmr?

Given that:

  1. The Security Policy does not tell anything about backporting
  2. otelhttp is an experimental (non-stable) Go module
  3. We lack "developer-power"

I honestly think that we will be not able to backport the fix, unless someone would volunteer to drive it.

Secured releases of older pinned semconv in use for each of the packages.

This is not clear. Also I am not what which semconv are you worried about. otelhttp scheme URL is not changed for a while. My guess is that the problem is with resources scheme URL. If that is the case then cannot you use https://github.com/MrAlias/otel-schema-utils to convert the resource to your expected scheme URL?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working response needed Waiting on user input before progress can be made
Projects
None yet
Development

No branches or pull requests

2 participants