-
Notifications
You must be signed in to change notification settings - Fork 82
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
[CVE][HIGH] CVE-2021-40690 Updating xmlsec library #306
base: 7.67.x-blue
Are you sure you want to change the base?
Conversation
This doesn't seem like it has anything to do with this PR. |
jenkins do fdb |
jenkins run cdb |
jenkins run fdb |
Bad classfile on a GWT class. Is this happening in other PRs? |
Are we trying to get full green builds here? |
Does this happen also locally, when you build without your change, please? |
Fixes a CVE in xmlsec. Signed-off-by: Jason Porter <[email protected]> Bumping to same version we have elsewhere Signed-off-by: Jason Porter <[email protected]>
cd3ad8a
to
2af05ad
Compare
I haven't seen it yet, but maybe I'm not running the commands/order as CI? |
This doesn't seem to have a problem when I run it locally. Is it even needed here? Signed-off-by: Jason Porter <[email protected]>
jenkins run cdb |
Well, here's the failure:
But I don't see why it couldn't create the directory. Permissions? Space? Something else? Anyone have any ideas? |
jenkins run cdb |
1 similar comment
jenkins run cdb |
Latest one looks like kafka errors with the testcontainer. Are we seeing this elsewhere? |
jenkins run cdb |
1 similar comment
jenkins run cdb |
I think this is the error:
It continues down to v1. That doesn't seem like anything I have done in this PR. |
jenkins run cdb |
Fixes a CVE in xmlsec.
There's a CVE in the version of xmlsec that we use, it was fixed in 2.2.3, but we're also using version 2.2.6 elsewhere in the codebase, so I figured it made sense to use the same version in both places.