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
Script - Workaround instructions to address CVE-2021-44228 in vCenter Server 
Readme
# vCenter Server Workaround instructions CVE-2021-44228
 Workaround instructions to address CVE-2021-44228 in vCenter Server 

VMware vCenter log4j workaround
This is the workaround VMware vCenter log4j vulnerability CVE-2021-44228 processs put together as a single script

VMware have released a python script linked on the KB article (works Much better :-)

If you don't like quick and dirty..
Apply workarounds and verify

cve-workaround
Run verification only

cve-workaround -v
Rollback - very basic, copies the .bak files over the patched files, restarts the services, and prints status messages.
cve-workaround -rollback
PSC Client Service for 6.5 - thank you to Power-Wagon on reddit for verifying
cve-workaround -sprayandpray65

Simple steps:
SSH to vCenter
Type shell to enter shell mode
Paste entire contents of script
Type cve, hit tab, enter
And you're done.

The Process:
Automatically detects the version and required steps
Backs up existing files to .bak files
Applies the workarounds recommended by VMware
Skips any steps that are already applied
Reports status as it goes
Provides a summary at the end - verification is more accurate / granular than the KB steps

File Snapshot

[4.0K] /data/pocs/3c1b11fbf1ffb4c4520e22faf275fd0db9beeda0 ├── [1.2K] README.md └── [ 12K] run-cve-patch.sh 0 directories, 2 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 →