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.

Sign up for GitHub

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

Jump to bottom

Does CVE-2020-36518 affect jackson-databind 2.13.2.1 ? #3674

Closed
BadTrasher opened this issue Nov 18, 2022 · 4 comments
Closed

Does CVE-2020-36518 affect jackson-databind 2.13.2.1 ? #3674

BadTrasher opened this issue Nov 18, 2022 · 4 comments
Labels
to-evaluate Issue that has been received but not yet evaluated

Comments

@BadTrasher
Copy link

No description provided.

@BadTrasher BadTrasher added the to-evaluate Issue that has been received but not yet evaluated label Nov 18, 2022
@cowtowncoder
Copy link
Member

No. I'll update #2816 to more clearly indicate fixed-in version.

@BadTrasher
Copy link
Author

BadTrasher commented Nov 19, 2022 •
edited

https://nvd.nist.gov/vuln/detail/CVE-2020-36518
image
But I see that on NVD this version shows affected

@BadTrasher
Copy link
Author

If I do not use jackson-bom, Does it affect ?
image

@cowtowncoder
Copy link
Member

BOMs only define sets of versions: so what matters is specific version of jackson-databind, not whether version came from BOM or not.
Put another way: use of BOM is NOT required to have version with fix -- if you have 2.13.2.1 or 2.13.2.2 you are good.

Hope this helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
to-evaluate Issue that has been received but not yet evaluated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cowtowncoder @BadTrasher