Experiment 10

The document discusses the Log4Shell vulnerability discovered in December 2021, which exposed numerous systems to remote code execution attacks due to a flaw in the widely used Apache Log4j framework. It highlights the rapid global response and mitigation efforts, including the release of fixes and the impact on both governmental and personal devices. The analysis indicates a significant level of exploitation within a short timeframe, likening the situation to a cyber pandemic.

Uploaded by

sonawanelitesh92

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

3 views3 pages

Experiment 10

Uploaded by

sonawanelitesh92

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 3

Experiment 10.

Case Study

Aim: Examine real-world data breaches & cryptographic failures, highlighting key lessons learned

Log4shell Vulnerability

Introduction:
In December 2021, the cybersecurity community faced one of the most severe vulnerabilities in

recent memory.

Log4j, this zero-day vulnerability in Apache Log 4 2 exposed countless systems to remote code execution
(RCE) attacks. its widespread use in Java. applications meant that a broad spectrum of software, from
enterprise applications to closed and cloud services, was vulnerable. This case study explores the technical
aspects of Log4Shell, its impact, and the global response to mitigate it. The vulnerability had existed
unnoticed since 2013 and was privately disclosed to the Apache software team, the foundation of which
Loges is a project, by Chenzhajun of Allihabe is the cloud's security team, on 24 November 2021

Background:-
Log4s is an open-source logging framework that allows s/w developers to log data within their app and can
include user input. It is used ubiquitously-Usually in Java applications, especially in enterprise. S/w originally
written in 2001 by Ceki Gules, it is now part of Apache logging services, a project of the Apache Software
Foundation.

Mitigation:-
Fixes for the vulnerability were released on 6 December 2021. These days, before the vulnerability was
published in the latest version 2.15 or earlier.

The Rix includes restricting the servers and protocols that may be used for lookups, Researchers discovered
a related bug, CVE-2021-45045, that allows local or remote code execution in certain non-default
configurations and was fixed in version 2.16.0, which disabled all features wing INDL

Usage:-
The exploit allows hackers to gain control of vulnerabilities in devices using Java, and some hackers employ
it. The vulnerability to use victim devices for exploitation mining, creating botnets, sending spam,
establishing back doors, and other illegal activities, such as ransomware attacks, in the days following the
vulnerability.
Response and impact:
Governmental:-
In the United States, the director of the Cybersecurity and the Infrastructure Security Agency (CISA), Jen
Easterly, described the exploit as one of the most serious I've seen in my entire career, if not most Serious",
explaining that hundreds of millions of devices were attacked and advising vendors to prioritize s/w updates.

Privacy:-
Some personal devices are connected to the internet, such as small TVs and security cameras, which are
vulnerable to exploitation. Some s/w may never get the patch due to discontinued manufacturing support.

Analysis:-
As of 14 Dec. 2021, almost half of all corporate alerts globally have been actively probed, with over 50
percent of the exploits having been produced within 24 hours. Check Point's s/w Technologies in a detailed
analysis described the s/w situation as being a true cyber pandemic, and characteristically, the potential for
damage.