LexisNexis Breach Incident Score: Analysis & Impact (LEX1772815548)

In this Rankiteo incident briefing, we review the LexisNexis breach identified under incident ID LEX1772815548.

The analysis begins with a detailed overview of LexisNexis's information like the linkedin page: https://www.linkedin.com/company/lexisnexis, the number of followers: 391074, the industry type: IT Services and IT Consulting and the number of employees: 10705 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 706 and after the incident was 628 with a difference of -78 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on LexisNexis and their customers.

LexisNexis recently reported "LexisNexis Breach Exposes Millions of Records Due to Unpatched React Vulnerability", a noteworthy cybersecurity incident.

A major data breach at LexisNexis, a provider of legal and data analytics services to governments and corporations in over 150 countries, has exposed nearly 4 million records, including customer accounts, password hashes, and cloud infrastructure details.

The disruption is felt across the environment, affecting AWS containers, legacy servers, and exposing 3.9 million database records, 21,042 customer accounts, 5,582 attorney survey responses, 45 employee password hashes, 53 AWS Secrets Manager secrets, VPC infrastructure mapping, with nearly 3.9 million records at risk.

In response, and stakeholders are being briefed through Affected customers notified.

The case underscores how Ongoing, teams are taking away lessons such as Failure to apply critical patches and persistent cybersecurity weaknesses due to outdated software, and recommending next steps like Apply critical patches promptly, enhance cloud security configurations, and conduct regular vulnerability assessments, with advisories going out to stakeholders covering Affected customers notified.

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploit Public-Facing Application (T1190) with high confidence (90%), supported by evidence indicating exploited an unpatched React2Shell vulnerability in the company’s systems. Under the Execution tactic, the analysis identified Exploitation for Client Execution (T1203) with moderate to high confidence (80%), supported by evidence indicating react2Shell vulnerability allowed attackers to execute malicious code. Under the Persistence tactic, the analysis identified Account Manipulation (T1098) with moderate confidence (60%), supported by evidence indicating aWS Secrets Manager secrets in plaintext exposed (53 secrets). Under the Privilege Escalation tactic, the analysis identified Exploitation for Privilege Escalation (T1068) with moderate to high confidence (70%), supported by evidence indicating insecure cloud configurations leveraged to access AWS containers. Under the Defense Evasion tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating aWS Secrets Manager secrets exposed, potentially used for access and Hijack Execution Flow: DLL Side-Loading (T1574.002) with moderate confidence (50%), supported by evidence indicating react2Shell vulnerability may have enabled DLL side-loading. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials In Files (T1552.001) with high confidence (90%), supported by evidence indicating 53 AWS Secrets Manager secrets in plaintext exposed and OS Credential Dumping: /etc/passwd and /etc/shadow (T1003.008) with moderate confidence (60%), supported by evidence indicating 45 employee password hashes compromised. Under the Discovery tactic, the analysis identified Account Discovery: Cloud Account (T1087.004) with moderate to high confidence (80%), supported by evidence indicating complete VPC infrastructure mapping exposed and Network Service Discovery (T1046) with moderate to high confidence (70%), supported by evidence indicating aWS containers accessed, infrastructure details exposed. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating 3.9M records, customer accounts, attorney survey responses collected and Data from Cloud Storage (T1530) with high confidence (90%), supported by evidence indicating aWS containers accessed, 2GB of data exfiltrated. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating 2GB of stolen information dumped on dark web platforms and Transfer Data to Cloud Account (T1537) with moderate to high confidence (70%), supported by evidence indicating data exfiltrated from AWS containers to attacker-controlled locations. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (40%), supported by evidence indicating legacy data pre-2020 compromised, potential integrity impact and Defacement: Internal Defacement (T1491.001) with lower confidence (30%), supported by evidence indicating vPC infrastructure mapping exposed, potential for misuse. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.