Skip to content

Update Log4J2 Version #38

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

Closed
feinstein opened this issue Dec 12, 2017 · 2 comments
Closed

Update Log4J2 Version #38

feinstein opened this issue Dec 12, 2017 · 2 comments

Comments

@feinstein
Copy link

Log4j2 is currently on version 2.10.0 and this library is still referencing version 2.8.2.

Please update the library.

@carlzogh
Copy link
Contributor

carlzogh commented May 20, 2020

Hey @feinstein - Log4j dependencies have been updated to 2.13.2 as part of aws-lambda-java-log4j2 version 1.2.0.

ref: https://github.com/aws/aws-lambda-java-libs/blob/master/aws-lambda-java-log4j2/RELEASE.CHANGELOG.md

@feinstein
Copy link
Author

Thanks, but seriously you guys need to rethink your worfklow. It took 2 years and a half to update a library reference.

This is specially troublesome as "Using Components with Known Vulnerabilities" is the OWASP 9th most security risk.

dtorok added a commit that referenced this issue Sep 4, 2023
* [alc] fix nullpointer exception when logging null

---------

Co-authored-by: Daniel Torok <[email protected]>
smirnoal pushed a commit that referenced this issue Sep 4, 2023
* [alc] fix nullpointer exception when logging null

---------

Co-authored-by: Daniel Torok <[email protected]>
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

No branches or pull requests

2 participants