Cyber risk and advisory programs that identify security gaps and build strategies to address them.
MDR that provides improved detection, 24/7 threat hunting, end-to-end coverage and most of all, complete Response.
Our team delivers the fastest response time in the industry. Threat suppression within just 4 hours of being engaged.
Be protected by the best from Day 1.
24/7 Threat Investigation and Response.
Expert hunting, research and content.
Defend brute force attacks, active intrusions and unauthorized scans.
Safeguard endpoints 24/7 by isolating and remediating threats to prevent lateral spread.
Investigation and enhanced threat detection across multi-cloud or hybrid environments.
Configuration escalations, policy and posture management.
Detects malicious insider behavior leveraging Machine Learning models.
Customer testimonials and case studies.
Stories on cyberattacks, customers, employees, and more.
Cyber incident, analyst, and thought leadership reports.
Demonstrations, seminars and presentations on cybersecurity topics.
Information and solution briefs for our services.
MITRE ATT&CK Framework, Cybersecurity Assessment, SOC Calculator & more
eSentire will be hosting a virtual webinar.
Join us for a live webinar with Keegan Keplinger, Research and Reporting…
eSentire will be hosting this event.
On December 9th, security researchers released details and Proof-of-Concept (PoC) exploit code for Remote Code Execution vulnerability impacting the Apache Log4j Java-based logging library. The vulnerability is now tracked as CVE-2021-44228 (CVSS: 10); exploitation will allow a remote and unauthenticated threat actor to take control of systems with vulnerable versions of Apache Log4j.
There are reports of ongoing exploitation of CVE-2021-44228 in the wild. eSentire has observed exploitation attempts as of December 10th, 2021. Organizations are strongly recommended to ensure security patches are deployed or alternative mitigations are enabled.
CVE-2021-44228 is alternatively known as Log4Shell or LogJam and impacts applications using Log4j 2.0-beta9 up to 2.14.1. The underlying issue resides in the Java Naming and Directory Interface (JNDI), which allows Java applications to access APIs for directory services such as LDAP or DNS. Vulnerable versions of Log4J do not sanitize user-input allowing an attacker to load a remote Java class file.
eSentire has observed opportunistic exploitation of this vulnerability to deliver cryptocurrency miner payloads and is taking action to block both the exploit and payload sources.
Example Log4J exploit string observed in User-Agent field of HTTP exploit attempt:
This vulnerability is high severity and impacts versions of Apache Log4j Java-based logging library, which is widely used in a variety of products, including major vendors. Organizations will need to ensure impacted products are patched as updates become available from vendors.
Google Cloud https://cloud.google.com/log4j2-security-advisory
A crowdsourced list of responses can be found here: https://gist.github.com/SwitHak/b66db3a06c2955a9cb71a8718970c592
Nationaal Cyber Security Centrum (NCSC-NL) has compiled a list of software and vulnerability status: https://github.com/NCSC-NL/log4shell/blob/main/software/README.md
Identifying use of Log4J in your environment will be important to limiting impact long term. Exploitation observed by eSentire is currently focused on deploying cryptominers via opportunistic attacks against internet-accessible services.
Identifying Log4J Jar Files:
A list of vulnerable Log4J-related files can be found here: https://github.com/mubix/CVE-2021-44228-Log4Shell-Hashes.
This list can be compared against your software inventory or located through a manual review of files on at-risk systems.
In Windows, JAR files may be located in C:\Program Files\ under the application name. For example:
C:\Program Files\someapplication\lib\log4j-core-2.13.3.jar. PowerShell methods for finding potentially vulnerable files can be found here.
In Linux occurrences of jar files can be traced to the application in question using the lsof command. For example: lsof /path/to/log4-core*.jar.
eSentire is actively blocking community feeds and exploitation sources observed across customers via our MDR for Network product.
https://gist.github.com/gnremy/c546c7911d5f876f263309d7161a7217 (source: GreyNoise Intelligence)