Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2021-44228 PoC — Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints

Source
Associated Vulnerability
Title:Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints (CVE-2021-44228)
Description:Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
Description
This repository contains a script that you can run on your (windows) machine to mitigate CVE-2021-44228
Readme
# Sitecore.Solr-log4j-mitigation CVE-2021-44228
This repository contains a script that you can run on your (windows) machine to mitigate CVE-2021-44228 by applying the advice as documented on https://solr.apache.org/security.html#apache-solr-affected-by-apache-log4j-cve-2021-44228

The PowerShell script assumes that you have used the default root path when installing Sitecore with the Sitecore Install Assistant on your development machine.
Use the script at your own risk, suggestions and modifications are welcome via pullrequests.

# CVE-2021-45046 update
There is a second script added that is able to replace Log2j with the desired version. It will stop and start the service of there is one that is found based on the directory name of your instance. When the script stumbles on an error it might be the case that your Solr instance is named different then determined from the location where you have Solr running.
 

File Snapshot

[4.0K] /data/pocs/7557d0d2635b6823d36544d9b8d43958252fde31 ├── [ 927] README.md ├── [6.4K] solr-log4j-autoupdate.ps1 ├── [1.4K] solr-log4j.ps1 └── [ 27] solr-log4j-upgrade-log2j.ps1 0 directories, 4 files
Shenlong Bot has cached this for you
Remarks
    1. It is advised to access via the original source first.
    2. Local POC snapshots are reserved for subscribers — if the original source is unavailable, the local mirror is part of the paid plan.
    3. Mirroring, verifying, and maintaining this POC archive takes ongoing effort, so local snapshots are a paid feature. Your subscription keeps the archive online — thank you for the support. View subscription plans →