-
Notifications
You must be signed in to change notification settings - Fork 209
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
Explicitly declaring xstream to override a transitively imported version affected by CVE #3785
Conversation
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.
Thanks @yesamer LGTM!
Thanks @yesamer , but I'm still doubtful about this modification. Here's from the build logs
To be clear, I'm not saying that the fix does not work as expected But IMO, this solution is inherently frail, since, without explicitly excluding xstream from quarkus-junit5:
At the same time, I see that, with the exclude, we would require another modification somewhere else... |
@gitgabrio I understand your concern and I agree this is not the ideal solution and in normal conditions it should be avoided, in my opinion, could make sense as a temporary solution but let's wait for other opinions. |
…ion affected by CVE (apache#3785) * exclude_xstream * Updated comment * change * change * change * change
Temporary declaring xstream dependency, a version (1.4.20) is transitively imported by Quarkus 3.8 affected by CVE