-
Notifications
You must be signed in to change notification settings - Fork 3.8k
unpin snakeyaml, add suppressions and licenses #15549
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
Changes from all commits
3249af4
2543ef8
540d502
319b2b6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -275,12 +275,23 @@ | |
| </suppress> | ||
|
|
||
| <suppress> | ||
| <!-- We need to wait for 17.0.0 of https://github.com/kubernetes-client/java/releases --> | ||
| <!-- We need to update several other components to move to Snakeyaml 2.0 to address CVE-2022-1471 --> | ||
| <!-- Snakeyaml 1.33 added to dependencyManagement in main pom file --> | ||
| <!-- The main use of snakeyaml in Druid is coming in test scope from: | ||
| com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:jar:2.12.7 | ||
| (version 1.27) | ||
| The contrib extension: druid-cassandra-storage uses version 1.6 in compile | ||
| scope | ||
| The integration tests use version 1.27 in compile scope. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. do we know where 1.27 comes from in integration tests? It would be nice if we could upgrade integration tests to 2.x as well.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. it's transitive dependency of:
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. let's update the version since we pin integration tests to 1.33 and not 1.27
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. if this is more hairy, we can do the jackson upgrade as a follow-up |
||
| Previous pinning of version to 1.33 forced the usage of the version across | ||
| all the modules, downgrading the version for some of them. | ||
| The removal of the pin in the main POM allows the modules choose which version | ||
| to be used, enabling the users to disable contrib extensions and use the | ||
| CVE free version of Snakeyaml in core extensions. | ||
| --> | ||
|
|
||
| <notes><![CDATA[ | ||
| file name: snakeyaml-1.33.jar | ||
| file name: snakeyaml-1.27.jar snakeyaml-1.33.jar | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we shouldn't be regressing here and have everything at least on 1.33 like we did before. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is just for completeness as snakeyaml is not packaged in the standard distribution There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
| ]]></notes> | ||
| <!-- Snakeyaml is used only in test scope in Druid core with trusted inputs --> | ||
| <cve>CVE-2022-1471</cve> | ||
| <!-- false positive --> | ||
| <cve>CVE-2023-2251</cve> | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.