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

Jackson 2.13.x compatibility #30199

Closed
meier-th opened this issue Mar 14, 2022 · 1 comment
Closed

Jackson 2.13.x compatibility #30199

meier-th opened this issue Mar 14, 2022 · 1 comment
Labels
status: invalid An issue that we don't feel is valid

Comments

@meier-th
Copy link

meier-th commented Mar 14, 2022

jackson-databind before 2.13.0 allows a Java StackOverflow exception and denial of service via a large depth of nested objects. Spring Boot 2.5.x brings in the version 2.12.6. Since 2.12.x and 2.13.x are different major versions, the compatibility issue arises.
Therefore, requesting you to clarify if jackson 2.13.x is compatible with Spring Boot 2.5.x

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Mar 14, 2022
@bclozel
Copy link
Member

bclozel commented Mar 14, 2022

I guess this is related to FasterXML/jackson-databind#2816 (comment)

From the looks of #28298, it doesn't seem this has introduced breaking changes.

I'm not sure creating issues like this one and #29569 really helps. We have a clear upgrade policy and 3rd party project maintainers choose to backport or not fixes. While we can point to obvious incompatibilities between versions, this is just valid for our own build and test suite. What I mean is: even if this comment says that it doesn't look incompatible from our perspective, it may very well break your application if it is using a feature that we don't. The best course of action here is to run your test suite against this version.

@bclozel bclozel added status: invalid An issue that we don't feel is valid and removed status: waiting-for-triage An issue we've not yet triaged labels Mar 14, 2022
@bclozel bclozel closed this as completed Mar 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: invalid An issue that we don't feel is valid
Projects
None yet
Development

No branches or pull requests

3 participants