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

Patch known Log4J RCE security vulnerability #28981

Closed
andersthorbeck opened this issue Dec 10, 2021 · 2 comments
Closed

Patch known Log4J RCE security vulnerability #28981

andersthorbeck opened this issue Dec 10, 2021 · 2 comments
Labels
status: duplicate A duplicate of another issue

Comments

@andersthorbeck
Copy link

See https://www.lunasec.io/docs/blog/log4j-zero-day/ and https://www.randori.com/blog/cve-2021-44228/.

Brief summary: a Remote Code Execution vulnerability was discovered yesterday in Log4J between versions 2.0 and 2.14.1 inclusive.
This vulnerability was patched in the most recent release, 2.15.0.

I see that the Spring Boot Logging Starter has a dependency to org.apache.logging.log4j:log4j-to-slf4j, at version 2.14.1, a vulnerable version.

From what I can tell, log4j-to-slf4j is the only artifact of the group org.apache.logging.log4j to which Spring Boot has any dependency. I am unsure whether this artifact alone exposes this vulnerability, or if only the log4j-core artifact is vulnerable.

Raising this issue as a "better safe than sorry" measure, to discern if Spring is left vulnerable here, and patch to most recent version if so.

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

wilkinsona commented Dec 10, 2021

Duplicates #28978 and #28958. It is only the log4j-core artifact that is vulnerable.

@wilkinsona wilkinsona added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged labels Dec 10, 2021
@andersthorbeck
Copy link
Author

Ah, apologies, I see now that I only searched in open issues before I created this one, not also in closed issues.
Thank you for your swift response!

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

3 participants