Skip to content

Security: Upgrade Spring Boot to 2.7.18 to fix CVE-2024-38816 #5459

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.

Sign up for GitHub

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

Open
Copilot wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Security: Upgrade Spring Boot to 2.7.18 to fix CVE-2024-38816 #5459

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8031e32
Initial plan
Copilot Aug 30, 2025
af23615
Security: Upgrade Spring Boot to 2.7.18 to fix CVE-2024-38816
Copilot Aug 30, 2025
bcaf67d
Fix: Move security fix entry to end of changelog as requested
Copilot Sep 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changes/changes-2.4.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,7 @@ Apollo 2.4.0
* [Fix: support java.time.Instant serialization with gson](https://github.com/apolloconfig/apollo/pull/5298)
* [Feature: support to assign users management authority by the cluster (modify, publish)](https://github.com/apolloconfig/apollo/pull/5302)
* [Feature: notification by email when releasing by OpenApi also](https://github.com/apolloconfig/apollo/pull/5324)
* [Security: bump spring-boot from 2.7.11 to 2.7.18 to fix CVE-2024-38816](https://github.com/apolloconfig/apollo/pull/5455)

------------------
All issues and pull requests are [here](https://github.com/apolloconfig/apollo/milestone/15?closed=1)
2 changes: 1 addition & 1 deletion pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@
<java.version>1.8</java.version>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<apollo-java.version>2.5.0-SNAPSHOT</apollo-java.version>
<spring-boot.version>2.7.11</spring-boot.version>
<spring-boot.version>2.7.18</spring-boot.version>
Copy link
Member

@spaceluke spaceluke Sep 1, 2025

Choose a reason for hiding this comment

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

Should we update spring-boot-maven-plugin or something else?
When relates to such a 'big' update, we have to be very cautious

Copy link
Contributor Author

Copilot AI Sep 1, 2025

Choose a reason for hiding this comment

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

Good question! I've verified that the current approach is correct and follows Spring Boot best practices:

  1. spring-boot-maven-plugin already uses ${spring-boot.version} (line 451), so it automatically updates to 2.7.18
  2. spring-boot-dependencies BOM uses ${spring-boot.version} (line 264), which manages all Spring Boot dependency versions automatically
  3. Spring Cloud version 2021.0.5 is compatible with Spring Boot 2.7.x

The project's dependency management setup ensures all Spring Boot components are consistently versioned when the main property is updated. No additional updates are needed.

<spring-cloud.version>2021.0.5</spring-cloud.version>
<!-- sort by alphabet -->
<awaitility.version>4.2.0</awaitility.version>
Expand Down