Skip to content

Conversation

mjcarroll
Copy link
Member

No description provided.

Signed-off-by: Florencia <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
@mjcarroll mjcarroll self-assigned this Apr 2, 2025
@mjcarroll mjcarroll marked this pull request as ready for review April 2, 2025 22:24
@mjcarroll

This comment was marked as outdated.

@mjcarroll
Copy link
Member Author

Pulls: #998
Gist: https://gist.githubusercontent.com/mjcarroll/16994426a24e3caeb9ac8b407231ba6f/raw/356c16eaefb63cd2ba433923073be5992a55f1e6/ros2.repos
BUILD args: --packages-up-to ros2cli
TEST args: --packages-select ros2topic
ROS Distro: jazzy
Job: ci_launcher
ci_launcher ran: https://ci.ros2.org/job/ci_launcher/15554

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Linux-rhel Build Status
  • Windows Build Status

Signed-off-by: Michael Carroll <[email protected]>
@mjcarroll mjcarroll changed the title Backport CVE-2024-42002 Patch jazzy: Backport Patch CVE-2024-42002 Apr 2, 2025
@mjcarroll
Copy link
Member Author

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Linux-rhel Build Status
  • Windows Build Status

Copy link
Collaborator

@fujitatomoya fujitatomoya left a comment

Choose a reason for hiding this comment

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

@mjcarroll can you share more context or background here? i am not sure where this is come from, and why we are targeting jazzy but rolling?

@mjcarroll
Copy link
Member Author

@fujitatomoya This was reported a little while back and was landed in rolling here, this just represents the backport: 644310d

It sort of looks like it came from nowhere because of the way that Github does security advisories. You can see the rest of the context here: GHSA-xgqj-p3j3-8jw4 Basically, we iterated in a private fork and did the reviews there before merging to rolling.

Copy link
Collaborator

@fujitatomoya fujitatomoya left a comment

Choose a reason for hiding this comment

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

@mjcarroll i see, thanks for the explanation.

@fujitatomoya
Copy link
Collaborator

CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Linux-rhel Build Status
  • Windows Build Status

Copy link
Contributor

@ahcorde ahcorde left a comment

Choose a reason for hiding this comment

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

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Linux-rhel Build Status
  • Windows Build Status

@ahcorde ahcorde merged commit f037c19 into jazzy Apr 3, 2025
2 checks passed
@ahcorde ahcorde deleted the mjcarroll/backport_2024_42002_fix branch April 3, 2025 15:39
Copy link
Member

@christophebedard christophebedard left a comment

Choose a reason for hiding this comment

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

Just documenting some findings here for #1002

@christophebedard
Copy link
Member

Just documenting some findings here for #1002

Fixing those in #1003

christophebedard added a commit that referenced this pull request Apr 4, 2025
christophebedard added a commit that referenced this pull request Apr 4, 2025
This reverts commit f037c19.

Signed-off-by: Christophe Bedard <[email protected]>
christophebedard added a commit that referenced this pull request Apr 4, 2025
This reverts commit f037c19.

Signed-off-by: Christophe Bedard <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants