-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Upgrade snakeyaml to 2.0 #24636
Upgrade snakeyaml to 2.0 #24636
Conversation
The more information could be found here: https://www.veracode.com/blog/research/resolving-cve-2022-1471-snakeyaml-20-release-0 I'm not sure |
The test fails
It seems that we need to fix in |
Well, |
I am considering shading all dependencies of ShardingSphere at a later time so that I won't need to worry about compatibility issues with Spring or other third-party libraries. |
Thanks @terrymanu for taking care of the upgarding. I did some works on We need to be very careful about these CVE issues. Anyway, if I understand correctly, we only use |
Also do we consider to enable Maybe we need to open a ticket for Apache Infra team? |
Thanks for your suggestion. |
Hmm, I can not see it because I'm not a committor? |
I cannot see camel's security tab either. |
Yeah, that makes sense. Anyway, CVE-2022-1471 is marked as |
Yes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- As an additional topic, consider that the Spring team doesn't expect to make big changes in SnakeYAML, they expect to handle it in Spring Framework 6.1, refer to Switch to Yaml 1.2 with snakeyaml-engine spring-projects/spring-framework#28349 and Upgrade to SnakeYAML 2.0 spring-projects/spring-framework#30048 , should I close Markup SpringBoot users need to specify SnakeYAML version in Github Wiki #21476 to wait for our shade operation on SnakeYAML?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes need upgrade to support snakeyml 1.33 to 2.1
|
This changed code is fully compatible with snakeyml 1.33, 2.0, 2.1. because The Representer class's old constructor Representer() was marked as Deprecated in 1.33 and then removed in version 2.0 "public Representer(DumperOptions options) " is exists in 1.33 ,2.0 and 2.1 . |
|
So is there any update on a new release of |
|
Thanks @linghengqian - Please raise this concern on the dev mailing list. It should be important to fix the security issue and hope it can be included in |
|
@linghengqian NP - I will take care of it. |
0f4153b
to
f189047
Compare
Hi @linghengqian Are you willing to release ElasticJob 3.0.4? |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-
@zhfeng ShardingSphere ElasticJob 3.0.4 with SnakeYAML 2.x is now available in https://repo1.maven.org/maven2/org/apache/shardingsphere/elasticjob/elasticjob-lite-core/3.0.4/ .
-
Do you feel like this needs to be a separate PR, or is it handled in the current PR?
@linghengqian feel free to rasie a new PR! |
|
Thanks @linghengqian and I close this PR. |
Fixes CVE-2022-1471
Changes proposed in this pull request:
Before committing this PR, I'm sure that I have checked the following options:
./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e
.