Ripple20

Ripple20 is a set of 19 vulnerabilities discovered in 2020 in a software library developed by the Cincinnati-based{{cite web|first=Catalin |last=Cimpanu |url=https://www.zdnet.com/article/ripple20-vulnerabilities-will-haunt-the-iot-landscape-for-years-to-come/ |title=Ripple20 vulnerabilities will haunt the IoT landscape for years to come |publisher=ZDNet |date=2018-08-21 |accessdate=2020-07-02}} company Treck Inc., which implemented a TCP/IP stack.{{cite web|first=Andy |last=Greenberg |url=https://www.wired.com/story/ripple20-iot-vulnerabilities/ |title=Ripple20 Bugs Put Hundreds of Millions of IoT Devices at Risk |publisher=WIRED |date=2020-06-16 |accessdate=2020-07-02}}{{Cite web |last=Coble |first=Sarah |date=2020-09-10 |title=Ripple20 a Major Threat |url=https://www.infosecurity-magazine.com/news/ripple20-a-major-threat/ |access-date=2024-06-20 |website=Infosecurity Magazine |language=en-gb}}{{Cite web |date=2020-09-15 |title=How to mitigate Ripple20 vulnerability risks |url=https://cybersecasia.net/news/warning-ripple20-vulnerability-may-be-the-next-gateway-for-hackers/ |access-date=2024-06-20 |website=CybersecAsia |language=en-US}}

The first release of Treck's library was around 1997. Treck had also worked with Elmic Systems, which created a fork of the library when the companies ended their collaboration.{{cite web|url=https://www.jsof-tech.com/ripple20/#ripple-disclosure | title=disclosure|website=jsof-tech.com|accessdate=2020-07-02}} In September 2019, JSOF researchers analyzed a device containing code from the library and discovered it had vulnerabilities. Further analysis determined that the code originated from Treck's library, which had been widely implemented by numerous manufacturers. The disclosure of the vulnerabilities was made in June 2020.{{cite web|url=https://www.darkreading.com/vulnerabilities---threats/ripple20-threatens-increasingly-connected-medical-devices/d/d-id/1338241 |title=Ripple20 Threatens Increasingly Connected Medical |publisher=Darkreading.com |date= |accessdate=2020-07-02}}{{cite web|url=https://hackaday.com/2020/06/26/this-week-in-security-bitdefender-ripple20-starbucks-and-pwned-passwords/ |title=This Week In Security: Bitdefender, Ripple20, Starbucks, And Pwned Passwords |publisher=Hackaday |date=2020-06-26 |accessdate=2020-07-02}}{{cite web|url=https://www.bleepingcomputer.com/news/security/list-of-ripple20-vulnerability-advisories-patches-and-updates/ |title=List of Ripple20 vulnerability advisories, patches, and updates |publisher=Bleepingcomputer.com |date=2020-06-25 |accessdate=2020-07-02}}{{cite web|url=https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-treck-ip-stack-JyBQ5GyC |title=Multiple Vulnerabilities in Treck IP Stack Affecting Cisco Products: June 2020 |publisher=Tools.cisco.com |date=2020-06-16 |accessdate=2020-07-02}} Ripple20 was chosen as the name for the set of vulnerabilities based on the disclosure year and the idea that the problems "rippled" through the supply chain from one company.{{cite web|url=https://www.jsof-tech.com/ripple20/#ripple=overview|title=Overview|website=jsof-tech.com|accessdate=2020-07-02}} It is difficult to identify all affected devices, because manufacturers may not realize that the library was used in one of their components.{{cite web|first=Jon |last=Gold |url=https://www.networkworld.com/article/3563842/ripple20-tcpip-flaws-can-be-patched-but-still-threaten-iot-devices.html |title=Ripple20 TCP/IP flaws can be patched but still threaten IoT devices |publisher=Network World |date= |accessdate=2020-07-02}}

{{reflist}}

• {{cite web|url=https://treck.com/vulnerability-response-information/|title=Vulnerability Response Information|website=treck.com}}

Category:Computer security exploits