https://www.iotworldtoday.com/wp-content/themes/ioti_child/assets/images/logo/mobile-logo.png
  • Home
  • News
    • Back
    • Roundups
  • Strategy
  • Special Reports
  • Business Resources
    • Back
    • Webinars
    • White Papers
    • Industry Perspectives
    • Featured Vendors
  • Other Content
    • Back
    • Q&As
    • Case Studies
    • Features
    • How-to
    • Opinion
    • Podcasts
    • Strategic Partners
    • Latest videos
  • More
    • Back
    • About Us
    • Contact
    • Advertise
    • Editorial Submissions
  • Events
    • Back
    • Embedded IoT World (Part of DesignCon) 2022
Iot World Today
  • NEWSLETTER
  • Home
  • News
    • Back
    • Roundups
  • Strategy
  • Special Reports
  • Business Resources
    • Back
    • Webinars
    • White Papers
    • Industry Perspectives
    • Featured Vendors
  • Other Content
    • Back
    • Q&As
    • Case Studies
    • Features
    • How-to
    • Opinion
    • Podcasts
    • Strategic Partners
    • Latest videos
  • More
    • Back
    • About Us
    • Contact
    • Advertise
    • Editorial Submissions
  • Events
    • Back
    • Embedded IoT World (Part of DesignCon) 2022
  • newsletter
  • IIoT
  • Cities
  • Energy
  • Homes/Buildings
  • Transportation/Logistics
  • Connected Health Care
  • Retail
  • AI
  • Metaverse
  • Development
  • Security
ioti.com

Security


Getty Images

IoT security

Protecting Your Network Against Ripple20 Vulnerabilities

Early this year, Ripple20 wrought havoc on numerous IoT devices, given vulnerable third-party code. Here are ways to prevent your organization from the fallout.
  • Written by Brien Posey
  • 25th January 2021

In the realm of technology, some events can disrupt the landscape and force practitioners to reevaluate daily operations.

Earlier this year, the arrival of the Ripple20 breach was that kind of event—reminding IT pros across the globe that vulnerable third-party code can wreak havoc on IT systems, opening the door to malicious attacks.

Earlier this year, the JSOF research lab discovered a series of vulnerabilities that became collectively known as Ripple20 (). The Ripple20 vulnerabilities exist within the Trek Inc. TCP/IP library, which is used by hundreds of millions of IoT devices ranging from industrial IoT devices to consumer grade devices used in the home. The affected software library has also been used in other types of connected devices such as point-of-sale terminals, medical equipment, and aviation-related devices. These vulnerabilities can be exploited for remote code execution and even complete device takeover. These code bugs have been difficult to track and remove because of the widespread adoption of this third-party code in various systems. Indeed, the bugs may never be fully patched in some products.

The seriousness of the Ripple20 vulnerabilities has been well established through various proof of concept demonstrations. At this point, organizations must work to determine whether they are using devices that are affected by this collection of vulnerabilities, and if so, how to go about addressing the problem.

Locating Ripple20-Affected Devices

Unfortunately, determining which of an organization’s devices are affected by the Ripple20 vulnerability is not an easy task. As previously noted, the vulnerability exists in a low-level software library that dozens of different vendors use. Because so many devices use this library, automated detection of the vulnerability is difficult at best.

But automated detection methods do exist, several tools help identify vulnerable devices. GitHub for example, contains a tool that is designed to passively monitor TCP/IP traffic flowing across a network to detect signs that devices suffer from the Ripple20 vulnerabilities.

Similarly, Forescout has released guidance to help IT pros detect Ripple20 vulnerabilities on their networks. ExtraHop has also developed a detection method.

As helpful as these tools might be, using them may not be an option for every organization. Smaller organizations for example, might lack the IT expertise to use such tools, or the licensing costs may be cost-prohibitive (although the GitHub tool is open source). If an organization can’t use the available tools to detect vulnerable devices, there is an alternative, albeit a much more tedious method, to use.

Here, an organization would method involves manually determining which of an organization’s devices suffer from the vulnerability.

The first step is to perform a comprehensive inventory of all network-connected devices. With a hardware inventory in hand, the next step is to look for devices manufactured by vendors whose products are known to be vulnerable. As of this writing, there are 31 vendors with vulnerable products, and dozens more are still being evaluated. There is the most recent list of affected vendors.

The list of includes links to each vendors’ Ripple20 response page, which for most of the affected vendors includes information about which devices are affected and on what the vendor is doing to address the vulnerability.

The best way to secure an affected device is to update the device’s firmware using a manufacturer-provided patch. Unfortunately, patching isn’t always an option. Some devices simply do not contain updatable firmware. Similarly, a manufacturer may not choose to offer patches for older devices that it no longer officially supports. It’s also possible that a vendor may still be in the process of developing or testing a patch, and does not yet have a patch available.

Organizations also have to consider the possibility that some of their devices may be vulnerable even though they do not appear on any of the lists of devices that are known to be problematic. After all, there are numerous vendors whose products are still being evaluated. Some vendors’ products will never be evaluated because the vendor is small and obscure or because it has gone out of business.

Alternative Options for Securing Affected Devices

If an organization has affected devices that cannot be patched or devices that are not confirmed but are suspected of being vulnerable, the organization will need to take other measures to protect itself. Ideally, insecure devices that cannot be made secure should be replaced with devices that known to be unaffected by the Ripple20 vulnerability. If this isn’t an option there are some things that can be done.

Make sure that potentially vulnerable devices are not accessible from the Internet. This is an extremely important step, because attacks against such devices generally originate in the outside world. If possible, organizations should also relocate potentially vulnerable devices to dedicated subnets that are isolated from the end-user network. This further reduces the chances of an attacker being able to access the device.

IT pros should also filter any traffic going to or from potentially vulnerable devices. Generally speaking, IoT devices only need to communicate with specific IP addresses. Therefore, it’s a good idea to block traffic to or from any other addresses. Firewalls should also be used to block traffic on any ports that are unnecessary, and it might even be possible to block IPv6 traffic without affecting the device’s functionality.

Tags: Network security Security Technologies

Related


  • IoT Security Firm to Acquire Medical Security Startup
    Claroty is set to acquire Medigate to grow its foothold in securing the Internet of Medical Things
  • Ransomware Attack Could Impact Paychecks
    The Kronos ransomware attack affected the company’s private cloud service over the weekend, knocking it offline just before the holidays
  • Image shows an abstract digital big data concept.
    BotenaGo Malware Targets Millions of IoT Devices
    AT&T Alien Labs identified the malware that has left millions of IoT devices exposed.
  • IoT Startup Raises $10M
    Platform aims to bolster network security with automated device configurations and visibility.

Leave a comment Cancel reply

-or-

Log in with your IoT World Today account

Alternatively, post a comment by completing the form below:

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Related Content

  • IoT Device Security at the Edge Poses Unique Challenges
  • Zero-Trust Security for IoT: Establishing Rigorous Device Defenses
  • AI Ups the Ante for IoT Cybersecurity
  • IoT Security Trends, 2021: COVID-19 Casts Long Shadow

Roundups

View all

IoT Product Roundup: PTC, Nokia, Arm and More

19th May 2022

IoT Deals, Partnerships Roundup: Intel, Nauto, Helium and more

14th May 2022

IoT Product Roundup: Amazon, Synaptics, Urban Control and More

27th April 2022

White Papers

View all

The Role of Manufacturing Technology in Continuous Improvement Ebook

6th April 2022

IIoT Platform Trends for Manufacturing in 2022

6th April 2022

Latest Videos

View all
Dylan Kennedy of EMQ

Embedded IoT World 2022: Dylan Kennedy of EMQ

Dylan Kennedy, EMQ’s VP of global operations, sat down with Chuck Martin at Embedded IoT World 2022.

Embedded IoT World 2022: Omdia’s Sang Oh Talks Vehicle Chip Shortage

Omdia’s automotive semiconductor analyst sits down with Chuck Martin at this year’s event

E-books

View all

How Remote Access Helps Enterprises Improve IT Service and Employee Satisfaction

12th January 2022

An Integrated Approach to IoT Security

6th November 2020

Webinars

View all

Rethinking the Database in the IoT Era

18th May 2022

Jumpstarting Industrial IoT solutions with an edge data management platform

12th May 2022

AI led Digital Transformation of Manufacturing: Time is NOW

9th December 2021

Special Reports

View all

Omdia’s Smart Home Market Dynamics Report

7th January 2022

Cybersecurity Protection Increasingly Depends on Machine Learning

28th October 2020

IoT Security Best Practices for Industry and Enterprise

20th October 2020

Twitter

IoTWorldToday, IoTWorldSeries

Europe’s First Automated Gas Station Convenience Store dlvr.it/SR45J9 https://t.co/eDJDJ7CxkI

25th May 2022
IoTWorldToday, IoTWorldSeries

Zero-Emission, Autonomous Cargo Ship Under Development dlvr.it/SR3xgb https://t.co/3oU7CrKWkW

25th May 2022
IoTWorldToday, IoTWorldSeries

Hannover Messe 2022: 5 Key Themes at This Year’s Show dlvr.it/SR3wtW https://t.co/j0fQUiU2LW

25th May 2022
IoTWorldToday, IoTWorldSeries

Can AI Help Stop Mass Shootings? dlvr.it/SR3tqK https://t.co/VxPBdajWA3

25th May 2022
IoTWorldToday, IoTWorldSeries

China has revealed an autonomous marine drone carrier dlvr.it/SR3qXs https://t.co/yMiiqeMNrZ

25th May 2022
IoTWorldToday, IoTWorldSeries

ISQ’s #UAV inspection drones will be on display at this year’s @hannover_messe dlvr.it/SR35dg https://t.co/U6QOQtMbGw

25th May 2022
IoTWorldToday, IoTWorldSeries

👀 Looking to integrate #AI into your manufacturing process? Explore how #manufacturers can begin the process of… twitter.com/i/web/status/1…

25th May 2022
IoTWorldToday, IoTWorldSeries

The U.S. Army is getting a 5G boost for #AR #VR capabilities from #5G network provider @OceusNetworks.… twitter.com/i/web/status/1…

24th May 2022

Newsletter

Sign up for IoT World Today newsletters: vertical industry coverage on Tuesdays and horizontal tech coverage on Thursdays.

Special Reports

Our Special Reports take an in-depth look at key topics within the IoT space. Download our latest reports.

Business Resources

Find the latest white papers and other resources from selected vendors.

Media Kit and Advertising

Want to reach our audience? Access our media kit.

DISCOVER MORE FROM INFORMA TECH

  • IoT World Series
  • Channel Futures
  • RISC-V
  • Dark Reading
  • ITPro Today
  • Web Hosting Talk

WORKING WITH US

  • Contact
  • About Us
  • Advertise
  • Login/Register

FOLLOW IoT World Today ON SOCIAL

  • Privacy
  • CCPA: “Do Not Sell My Data”
  • Cookies Policy
  • Terms
Copyright © 2022 Informa PLC. Informa PLC is registered in England and Wales with company number 8860726 whose registered and Head office is 5 Howick Place, London, SW1P 1WG.
This website uses cookies, including third party ones, to allow for analysis of how people use our website in order to improve your experience and our services. By continuing to use our website, you agree to the use of such cookies. Click here for more information on our Cookie Policy and Privacy Policy.
X