-
Notifications
You must be signed in to change notification settings - Fork 71
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
Tracking Log4J CVE-2021-44228 Fixes #2007
Labels
Comments
It would be helpful to see a list of affected components. SOLR certainly. Are there others? Or is this still being assessed? |
From the tech call
|
The Playbook PR is in need of a tester from outside of my organization. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Setting this up to track our responses to the Log4J security issue. https://www.sentinelone.com/blog/cve-2021-44228-staying-secure-apache-log4j-vulnerability/
Playbook
PR Islandora-Devops/islandora-playbook#209
Per initial instructions this PR sets a global environment variable as per the CVE announcement. This can also be done by hand, or the following to set Java settings directly:
The PR also includes a Solr version update which contains the latest version of Log4j. This will not force an update of an existing site, for that you should update Solr manually.
Additionally, the playbook now does a scan for Log4J 2.x JARs and directly removes the JndiLookup class where it is found. This is the surest mitigation so far.
Force update Solr
If you'd like to force Ansible to update Solr without losing your data, you can remove the two files noted in this comment on the Geerlingguy Solr project.
ISLE
Follow the discussion in the #ISLE channel on Islandora's Slack
The text was updated successfully, but these errors were encountered: