-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Fix protobuf vulnerability CVE-2024-7254, SNYK-JAVA-COMGOOGLEPROTOBUF-8055227, SNYK-JAVA-COMGOOGLEPROTOBUF-8055228 #16423
Comments
valenad1
changed the title
Fix protobuf vulnerability CVE-2024-7254
Fix protobuf vulnerability CVE-2024-7254, SNYK-JAVA-COMGOOGLEPROTOBUF-8055227, SNYK-JAVA-COMGOOGLEPROTOBUF-8055228
Oct 15, 2024
valenad1
added a commit
that referenced
this issue
Oct 21, 2024
… (#16426) * upgrade google-cloud-storage to newest * upgarde protobuf and exclude the one from hadoop-common
valenad1
added a commit
that referenced
this issue
Oct 22, 2024
valenad1
added a commit
that referenced
this issue
Oct 24, 2024
* downgrade google gcs * upgrade only protobuf
valenad1
added a commit
that referenced
this issue
Oct 24, 2024
valenad1
added a commit
that referenced
this issue
Oct 24, 2024
valenad1
added a commit
that referenced
this issue
Oct 24, 2024
This was
linked to
pull requests
Oct 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Stack-based Buffer Overflow [High Severity][https://security.snyk.io/vuln/SNYK-JAVA-COMGOOGLEPROTOBUF-8055227] in com.google.protobuf:[email protected]
introduced by unknown:/opt/.venv/lib/python3.12/site-packages/h2o/backend/bin/h2o.jar@unknown > com.google.protobuf:[email protected]
This issue was fixed in versions: 3.25.5, 4.27.5, 4.28.2
Stack-based Buffer Overflow [High Severity][https://security.snyk.io/vuln/SNYK-JAVA-COMGOOGLEPROTOBUF-8055228] in com.google.protobuf:[email protected] introduced by unknown:/opt/.venv/lib/python3.12/site-packages/h2o/backend/bin/h2o.jar@unknown > com.google.protobuf:[email protected]
This issue was fixed in versions: 3.25.5, 4.27.5, 4.28.2
The text was updated successfully, but these errors were encountered: