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

mitigate log4j 3rd party components risks #2333

Closed
vdelendik opened this issue Dec 15, 2021 · 1 comment
Closed

mitigate log4j 3rd party components risks #2333

vdelendik opened this issue Dec 15, 2021 · 1 comment
Labels
enhancement
Milestone
1.26.2

Comments

@vdelendik
Copy link
Contributor

https://logging.apache.org/log4j/2.x/security.html

until we move into the patched logstash and elasticsearch it is strongly recommend:

  1. disable any public access to logstash and elasticsearch as it is configured by default
  2. declare LOG4J_FORMAT_MSG_NO_LOOKUPS=true env var for both affected components
@vdelendik vdelendik added this to the 1.26.2 milestone Dec 15, 2021
vdelendik pushed a commit that referenced this issue Dec 15, 2021
#2333: declared LOG4J_FORMAT_MSG_NO_LOOKUPS=true for logstash and ela…
d05849b 
…sticsearch
vdelendik added a commit that referenced this issue Dec 15, 2021
@vdelendik
Merge pull request #2334 from zebrunner/develop
56980be 
#2333
@vdelendik
Copy link
Contributor Author

done.

@vdelendik vdelendik changed the title mitigate log4j 3rd party components risks for log4j vulnerability mitigate log4j 3rd party components risks Dec 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
1.26.2
Development

No branches or pull requests
1 participant
@vdelendik