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

Please provide an updated point release that includes the fixed log4j vulnerability #29111

Closed
Polve opened this issue Dec 18, 2021 · 5 comments
Closed
Labels
status: duplicate A duplicate of another issue

Comments

@Polve
Copy link

Polve commented Dec 18, 2021

if I understand correctly log4j is automatically used when used in a spring boot project (at least I found it in mine even without asking for it).

Since Log4J released a new 2.17.0 version with fixes for CVE-2021-45046 and CVE-2021-45105 it would be great if you could quickly release an update version that just fixes the dependencies in order to fix our apps in a short time.

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

bclozel commented Dec 18, 2021

As mentioned in our issue template:

  • Managed Dependency Upgrade
    You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome.

This is already covered by #28984 (and related issues) as well as our dedicated blog post. This will be released on December 23rd.

@bclozel bclozel closed this as completed Dec 18, 2021
@bclozel bclozel added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged labels Dec 18, 2021
@snicoll
Copy link
Member

snicoll commented Dec 18, 2021

if I understand correctly log4j is automatically used when used in a spring boot project (at least I found it in mine even without asking for it).

That is inaccurate. Spring Boot uses logback by default. The dedicated blog post cover also that using log4j-api and the slf4j bridge (which we provide by convenience) does not trigger any of those vulnerabilities. If you've not opt-in for log4j2, your app is not vulnerable.

@Polve
Copy link
Author

Polve commented Dec 18, 2021

But since even logback is vulnerable my app is vulnerable anyway.
Also, I verified it and the vulnerability is even quite easy to exploit.

So my request was to understand if it was possible to have a very fast turnaround for a new release with upgraded deps.

@snicoll
Copy link
Member

snicoll commented Dec 18, 2021

You don't need and you shouldn't need to wait for a release to upgrade your use of Logback or Log4J2. The blog post has already all the information that you're asking.

@Polve
Copy link
Author

Polve commented Dec 18, 2021

Right, but since I couldn't find any mention on how to upgrade logback I (wrongly) assumed I couldn't use a similar approach to force the dependency.
Then I tried to set the property logback.version and it worked.
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

4 participants