Skip to content
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 Jackson-databind #869

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Upgrade Jackson-databind #869

wants to merge 1 commit into from

Conversation

UcanInfosec
Copy link
Contributor

Upgrading Jackson-databind to mitigate CVEs in 2.13.2.2. This requires 2.13.4.2

@UcanInfosec
Copy link
Contributor Author

@shoothzj and @kallestenflo heres the pull request for the update to the jackson-databind CVE. This would resolve the CVE, but unsure if the tool can support this update

@UcanInfosec
Copy link
Contributor Author

@shoothzj Thanks for the approvals! Looking forward to this being merged

@UcanInfosec UcanInfosec closed this by deleting the head repository Oct 28, 2022
@UcanInfosec UcanInfosec reopened this Oct 28, 2022
@UcanInfosec
Copy link
Contributor Author

UcanInfosec commented Nov 21, 2022

Hey, wanted to circle back on this to see if this is something that will get merged. @shoothzj

@hunterino
Copy link

Curious about merge plan?

@UcanInfosec
Copy link
Contributor Author

I am too. Not sure whom to @ mention to get this merged

@UcanInfosec
Copy link
Contributor Author

@kallestenflo we had another request to fix this. How do we move forward? @shoothzj

@shoothzj
Copy link
Contributor

shoothzj commented Feb 2, 2023

I am sorry, I am not maintainer of this project. Let me see if I can send mail to him. @kallestenflo

@UcanInfosec
Copy link
Contributor Author

UcanInfosec commented Feb 2, 2023

@shoothzj thanks. Much appreciated. Sorry to bother. Might make sense to release the next version soon too after this gets merged to have that version fix the vulns

@UcanInfosec
Copy link
Contributor Author

Looks like this project could need a new maintainer?? @kallestenflo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants