{"id":35553,"date":"2020-06-16T19:09:50","date_gmt":"2020-06-16T19:09:50","guid":{"rendered":"https:\/\/packetstormsecurity.com\/news\/view\/31303\/Ripple20-Vulnerabilities-Will-Haunt-The-IoT-Landscape-For-Years-To-Come.html"},"modified":"2020-06-16T19:09:50","modified_gmt":"2020-06-16T19:09:50","slug":"ripple20-vulnerabilities-will-haunt-the-iot-landscape-for-years-to-come","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/ripple20-vulnerabilities-will-haunt-the-iot-landscape-for-years-to-come\/","title":{"rendered":"Ripple20 Vulnerabilities Will Haunt The IoT Landscape For Years To Come"},"content":{"rendered":"

\"Ripple20\"<\/span><\/p>\n

Cyber-security experts have revealed today 19 vulnerabilities in a small library designed in the 90s that has been widely used and integrated into countless of enterprise and consumer-grade products over the last 20+ years.<\/p>\n

The number if impacted products is estimated at “hundreds of millions” and includes products such as smart home devices, power grid equipment, healthcare systems, industrial gear, transportation systems, printers, routers, mobile\/satellite communications equipment, data center devices, commercial aircraft devices, various enterprise solutions, and many others.<\/p>\n

Experts now fear that all products using this library will most likely remain unpatched due to complex or untracked software supply chains.<\/p>\n

Problems arise from the fact that the library was not only used by equipment vendors directly but also integrated into other software suites, which means that many companies aren’t even aware that they’re using this particular piece of code, and the name of the vulnerable library doesn’t appear in their code manifests.<\/p>\n

The Ripple20 vulnerabilities<\/h3>\n

These vulnerabilities — collectively referred to as Ripple20<\/strong><\/a> — impact a small library developed by Cincinnati-based software company Treck<\/a>.<\/p>\n

The library, believed to have been first released in 1997, implements a lightweight TCP\/IP stack. Companies have been using this library for decades to allow their devices or software to connect to the internet via TCP\/IP connections.<\/p>\n

Since September 2019, researchers from JSOF<\/a>, a small boutique cyber consultancy firm located in Jerusalem, Israel, have been looking at Treck’s TCP\/IP stack, due to its broad footprint across the industrial, healthcare, and smart device market.<\/p>\n

\n<\/section>\n

Their work unearthed serious vulnerabilities, and the JSOF team has been working with CERT (computer emergency response teams) in different countries to coordinate the vulnerability disclosure and patching process.<\/p>\n

In an interview with ZDNet<\/em> last week, JSOF said this operation involved a lot of work and different steps, such as getting Treck on board, making sure Treck has patches on time, and then finding all the vulnerable equipment and reaching out to each of the impacted vendors.<\/p>\n

Efforts have been successful, Shlomi Oberman, chief executive officer at JSOF, has told ZDNet<\/em>. Oberman credited CERT\/CC for playing a major role in coordinating the vulnerability disclosure process with all impacted vendors.<\/p>\n

Treck, while reticent in the beginning and thinking it was the subject of an extortion attempt, is now fully on board, Oberman said.<\/p>\n

In an email to ZDNet<\/em> on Monday, Treck has confirmed that patches are now available for all the Ripple20 vulnerabilities.<\/p>\n

Work on Ripple20 only halfway done<\/h3>\n

But JSOF said the work on identifying all the vulnerable devices is not yet done. The researchers said they named the 19 vulnerabilities as Ripple20 not because they were 20 vulnerabilities in the beginning, but because of the ripple effect they’ll cause in the IoT landscape in 2020, and the years to come.<\/p>\n

Researchers say they only scratched the surface when it comes to discovering all the devices that have implemented Treck’s TCP\/IP library, and that many equipment vendors will need to verify their own code going forward.<\/p>\n

Oberman said that while not all of the Ripple20 vulnerabilities are severe, there are a few that are extremely dangerous, allowing attackers to take over vulnerable systems from a “remote” scenario.<\/p>\n

In a security advisory that will go live today and reviewed by ZDNet under embargo, the US Department of Homeland Security has attributed ratings of 10 and 9.8 on the CVSSv3 vulnerability severity scale (scale goes from 1 to 10) to four of the Ripple 20 vulnerabilities. These are:<\/p>\n

    \n
  • CVE-2020-11896<\/strong> – CVSSv3 score: 10 – Improper handling of length parameter inconsistency in IPv4\/UDP component when handling a packet sent by an unauthorized network attacker. This vulnerability may result in remote code execution.<\/li>\n
  • CVE-2020-11897<\/strong> – CVSSv3 score: 10 – Improper handling of length parameter inconsistency in IPv6 component when handling a packet sent by an unauthorized network attacker. This vulnerability may result in possible out-of-bounds write.<\/li>\n
  • CVE-2020-11898<\/strong> – CVSSv3 score: 9.8 – Improper handling of length parameter inconsistency in IPv4\/ICMPv4 component when handling a packet sent by an unauthorized network attacker. This vulnerability may result in exposure of sensitive information.<\/li>\n
  • CVE-2020-11899<\/strong> – CVSSv3 score: 9.8 – Improper input validation in IPv6 component when handling a packet sent by an unauthorized network attacker. This vulnerability may allow exposure of sensitive information.<\/li>\n<\/ul>\n

    These four vulnerabilities, when weaponized, could allow attackers to easily take over smart devices or any industrial or healthcare equipment. Attacks are possible via the internet if the devices are connected online, or from local networks if the attacker gains a foothold on an internal network (for example, via a compromised router).<\/p>\n

    These four vulnerabilities are ideal for both botnet operators, but also for targeted attacks. Testing all systems for the Ripple20 vulnerabilities and patching these four issues, in particular, should be a priority for all companies, primarily due to Treck’s large footprint across the software landscape.<\/p>\n

    \n