feat(dependencies): remove org.quartz-scheduler:quartz #6257
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yuekun0707
approved these changes
Mar 24, 2025
xxo1shine
approved these changes
Mar 24, 2025
CodeNinjaEvan
approved these changes
Mar 24, 2025
eodiandie
approved these changes
Mar 24, 2025
halibobo1205
force-pushed
the
feat/remove_quartz
branch
from
d098e4c to
ab4b70b
Compare
CodeNinjaEvan
approved these changes
Mar 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Remove
org.quartz-scheduler:quartzto avoid potential impacts CVE-2023-39017.Tip
Tron does not use this scenario for now.
Why are these changes required?
quartz-jobs 2.3.2and below was discovered to contain a code injection vulnerability in the componentorg.quartz.jobs.ee.jms.SendQueueMessageJob.execute. This vulnerability is exploited via passing an unchecked argument.Important
this is disputed by multiple parties because it is not plausible that untrusted user input would reach the code location where injection must occur.
This PR has been tested by:
Follow up
Extra details