[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #58724] Treck Ripple20 Issues in LWIP

From: Subhan Waizi
Subject: [lwip-devel] [bug #58724] Treck Ripple20 Issues in LWIP
Date: Wed, 8 Jul 2020 04:25:09 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36

Follow-up Comment #3, bug #58724 (project lwip):

> But if you have more details at hand, feel free to support us in checking if
these issues exist in lwIP.

Unfortunately I lack the technical background and implementation details
concerning the LwIP stack. I encountered some script that might reveal if your
product is affected by some / all of the Ripple20 vulnerabilities
(https://github.com/corelight/ripple20) but I'm not sure if that can be run as
easily on devices that don't run the Treck stack.

Well most of the 19 vulnerabilities had "improper handling of length parameter
- cwe id 130" and "improper input validation - cwe id 20" as their common cwe
(common weakness enumeration). The vulnerabilities with cwe id 130 seemed to
be the most severe ones (all of them having a security severity score above 9
according to CVSS which is defined as "likely to have a catastrophic adverse
effect on the organization or individuals associated with the organization
(e.g., employees, customers)." according to CVSS. 

We'd have different possibilities here:

Reassure that LwIP does have a decent amount of test cases for those common
weaknesses (20 and 130 - input validation of length and input data).

Give a try to the Ripple20 script and try to run it on a LwIP V1 and V2 device
if possible.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]