Menu

#Log4j

14 posts

Feed·
14 of 14 posts
A Log4j Retrospective  Part 3: Evolution — Payloads and Attack Diversification
📰
0

A Log4j Retrospective Part 3: Evolution — Payloads and Attack Diversification

Akamai·Charlie Gero·about 1 month ago
#fa2C0nq8
#dns#security#log4j#akamai#example#systems

What new Log4j attack vectors is Akamai seeing? Read what Akamai CTO Charlie Gero says about mitigating DNS and other protocols in part 3 of this 4-part series.

15s
Read More
Our Journey to Detect Log4j-Vulnerable Machines
📰
0

Our Journey to Detect Log4j-Vulnerable Machines

Akamai·Stiv Kupchik·about 1 month ago
#lTy808kf

Log4Shell (CVE-2021-44228) is a remote code execution (RCE) vulnerability in the Apache-foundation open-source logging library Log4j. It was published on December 9, 2021, and then all hell broke loose.…

15s
Read More
CVE-2021-44228 - Patching is Recommended for Evolving Zero Day Vulnerability in Apache Log4j that allows remote code execution (RCE)
📰
0

CVE-2021-44228 - Patching is Recommended for Evolving Zero Day Vulnerability in Apache Log4j that allows remote code execution (RCE)

Akamai·Akamai·about 1 month ago
#RnfPXYGY

Akamai has been monitoring the rapidly evolving developments of CVE-2021-44228. We have been working closely with our customers and internal application teams to mitigate the risks posed by the threat of unauthorized remote code execution.…

15s
Read More
CVE-2021-44228 - Zero Day Vulnerability in Apache Log4j that allows remote code execution (RCE)
📰
0

CVE-2021-44228 - Zero Day Vulnerability in Apache Log4j that allows remote code execution (RCE)

Akamai·Akamai·about 1 month ago
#EZV3qLBy

See how Akamai helped open-source logging library Log4j fight against a critical unauthenticated remote code execution (RCE) vulnerability and reduce customer exposure.

15s
Read More