• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer

My TechDecisions

  • COVID-19 Update
  • Best of Tech Decisions
  • Topics
    • Video
    • Audio
    • Mobility
    • Unified Communications
    • IT Infrastructure
    • Network Security
    • Physical Security
    • Facility
    • Compliance
  • RFP Resources
  • Resources
  • Podcasts
  • Subscribe
  • Project of the Week
  • Latest News
  • About Us
    SEARCH
Compliance, IT Infrastructure, Network Security, News

Should Log4Shell Still Keep CISOs Up at Night?

Invicti's Dan Murphy explains why CISOs shouldn't be worried about Log4Shell's impact, months after the Log4j threat.

June 7, 2022 Dan Murphy Leave a Comment

CISO, Log4shell, Log4j
feelartfeelant/stock.adobe.com

In December 2021, the Apache Software Foundation disclosed that the popular Log4j framework contained a critical vulnerability that allowed remote code execution (RCE).  It caused a security earthquake, keeping many CISOs up at night. The aftershocks are still felt.

The vulnerability, known as Log4Shell, was extremely easy to exploit. Put simply, it allowed any malicious attacker to remotely inject Java classes into a vulnerable process, allowing the attacker to do anything they wanted.

In response to the news, nearly every software vendor provided patches or tools to detect Log4j vulnerabilities. Now, months since the initial Log4j threat, CISOs wonder if they should still be worried about Log4j’s impact.

Is Log4Shell still an issue for organizations?

Invicti found that weekly detection rates are now less than 1% of what they were at the peak shortly after the Apache Software Foundation disclosed the vulnerability. Over 82% of Log4Shell vulnerabilities were confirmed to be fixed in subsequent dynamic scans of vulnerable applications.

As an industry, this is excellent news; it suggests that automated scanning of applications has helped detect and fix thousands of instances of vulnerabilities. However, something you think is secure today may not be tomorrow or even an hour from now, and organizations must check for security vulnerabilities continuously.

How can CISOs assess if Log4j is still in their environment?

It is best to fix vulnerabilities left in the development process while also implementing application security testing on the right (i.e., staging and production). As a start, security leaders can build software composition analysis (SCA) into the software development life cycle (SDLC) to ensure that software is scanned whenever it is changed as part of a CI/CD pipeline.

But the real danger with Log4Shell is older applications, and CISOs must be aware of this potential threat. These applications may be deployed without a modern CI/CD pipeline or may even be running on the network without active maintenance or development.

Older apps often live in dusty layers of application infrastructure, only invoked occasionally outside the typical execution flow. However, tools like asset discovery and dynamic application security testing (DAST) can scan applications with web and API interfaces to detect vulnerabilities.

It’s also important to work with a security tools vendor you trust to release timely updates when there are new exploits, like Log4Shell.

Why do new applications and pieces of software still contain Log4Shell months after disclosure?

Since modern software tends to be a patchwork of many disparate components, fixing Log4Shell vulnerabilities isn’t that simple. Sometimes these dependencies are transitive – a software developer adds an open-source package that depends on a package that then depends on Log4j. Because of this, the developer has no idea they introduced a vulnerable component into their code.

Related: Check Point Survey: CISOs’ Confidence In Security Dwindles As Cyber Attacks Increase

Other times, a newer customer-facing microservice calls into a legacy system that’s not directly exposed to the internet but is used in a new way, perhaps with more modern usage of an API. This more recent way of calling an API could result in data being passed differently, which causes the legacy system to issue a non-fatal warning log. But if that backend system isn’t patched, that log can contain an injection payload that ultimately exposes remote code execution (RCE). Because software systems aren’t simple, it isn’t enough to say: my software is secure enough. Your applications depend on plenty of other software, and those dependencies could be exposed in new ways, further allowing your application software to become exploited.

It’s been six months since Log4Shell, and while the threat landscape isn’t zero, knowing your organization’s entire attack surface is a critical first step to avoiding any future Log4j-related threats. In addition, adopting a continuous modern application security testing solution that allows for integrations, automation, and accuracy will help organizations stay ahead of future exposures.

So as a CISO, should you be up late at night worrying about Log4j? At this point, probably not if you have the right tools and plan in place. As the data suggests, regular security scanning will lead to the peace of mind you need to sleep more soundly.

Dan Murphy is a Distinguished Architect at Invicti.

 

Tagged With: Log4j, Log4Shell

Related Content:

  • Google Password Manager Google Updates Password Manager For Unified Experience
  • VMware vSphere+ vSAN+ VMware Releases vSphere+ and vSAN+ to Enhance On…
  • Microsoft Cybersecurity Architect Expert Microsoft Adds New Expert-level Cybersecurity Architect Certification
  • Microsoft Basic Auth Prepare: Microsoft Begins Disabling Basic Auth in Exchange…

Free downloadable guide you may like:

  • Uber Advanced Technologies Group Drives its Business Forward

    The guiding principle for the new Uber meeting room redesign was “invisible comfort” to ensure that everyone could maximize productivity.

Reader Interactions

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Get the FREE Tech Decisions eNewsletter

Sign up Today!

Latest Downloads

Uber Advanced Technologies Group Drives its Business Forward

The guiding principle for the new Uber meeting room redesign was “invisible comfort” to ensure that everyone could maximize productivity.

Windows 11
Blueprint Series: Upgrading to Windows 11

Upgrading end users to Windows 11 could be one of the most challenging tasks IT has to face in the coming years. Although the new version is touted...

The State of the IT Department in 2022

The role of the IT professional has shifted from one that supports the business to one that is deserving of a seat at the table when it comes to ma...

View All Downloads

Would you like your latest project featured on TechDecisions as Project of the Week?

Apply Today!
Sharp Microsoft Collaboration HQ Logo

Learn More About the
Windows Collaboration Display

More from Our Sister Publications

Get the latest news about AV integrators and Security installers from our sister publications:

Commercial IntegratorSecurity Sales

AV-iQ

Footer

TechDecisions

  • Home
  • Welcome to TechDecisions
  • Subscribe to the Newsletter
  • Contact Us
  • Media Solutions & Advertising
  • Comment Guidelines
  • RSS Feeds
  • Twitter
  • Facebook
  • Linkedin

Free Technology Guides

FREE Downloadable resources from TechDecisions provide timely insight into the issues that IT, A/V, and Security end-users, managers, and decision makers are facing in commercial, corporate, education, institutional, and other vertical markets

View all Guides
TD Project of the Week

Get your latest project featured on TechDecisions Project of the Week. Submit your work once and it will be eligible for all upcoming weeks.

Enter Today!
Emerald Logo
ABOUTCAREERSAUTHORIZED SERVICE PROVIDERSTERMS OF USEPRIVACY POLICY

© 2022 Emerald X, LLC. All rights reserved.