Skip to content

Fix CVE-2025-48734, CVE-2024-13009 (#36106)#36109

Merged
liferoad merged 1 commit intoapache:release-2.68from
liferoad:cherrypick_pr_36106
Sep 10, 2025
Merged

Fix CVE-2025-48734, CVE-2024-13009 (#36106)#36109
liferoad merged 1 commit intoapache:release-2.68from
liferoad:cherrypick_pr_36106

Conversation

@liferoad
Copy link
Copy Markdown
Contributor

@liferoad liferoad commented Sep 10, 2025

CP: #36106


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

* update dependencies due to CVE-2024-13009 and CVE-2025-24970

* update dependency due to transitive dependency with  CVE-2025-48734

* outstanding netty dependency.

* fix netty's CVE-2025-55163

* Revert "fix netty's CVE-2025-55163"

This reverts commit 874a77c.

* revert netty
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @liferoad, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the project's security posture by upgrading critical third-party library versions. These updates are specifically aimed at mitigating identified common vulnerabilities and exposures (CVEs), ensuring the stability and security of the application's components.

Highlights

  • Dependency Updates for Security Vulnerabilities: This PR updates several key dependencies to address known security vulnerabilities (CVE-2025-48734, CVE-2024-13009).
  • Hadoop Version Bump: The Hadoop dependency has been updated from version 3.4.1 to 3.4.2.
  • Jetty Version Bump: The Jetty server and servlet dependencies have been updated from 9.4.54.v20240208 to 9.4.57.v20241219.
  • Netty Version Bump: The Netty dependency has been updated from 4.1.51.Final to 4.1.110.Final.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@liferoad liferoad requested a review from Amar3tto September 10, 2025 17:56
@kennknowles kennknowles changed the base branch from release-2.68 to release-2.67.0-postrelease September 10, 2025 18:33
@kennknowles
Copy link
Copy Markdown
Member

When I switched to release-2.67.0-postrelease as base branch, it got conflicts.

@kennknowles kennknowles changed the base branch from release-2.67.0-postrelease to release-2.68 September 10, 2025 18:34
@kennknowles
Copy link
Copy Markdown
Member

My mistake - wrong CP

@github-actions
Copy link
Copy Markdown
Contributor

Assigning reviewers:

R: @Abacn for label java.
R: @damccorm for label build.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

@liferoad liferoad merged commit 3461a46 into apache:release-2.68 Sep 10, 2025
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants