Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a25363c60ab998f1

Jump to content

// Workers AI · dad joke modeDoes Ripple20 make waves?

From Wikipedia, the free encyclopedia
(Redirected from Treck Inc.)

Ripple20 is a set of vulnerabilities discovered in 2020 in a software library that implemented a TCP/IP stack. The security concerns were discovered by JSOF, which named the collective vulnerabilities for how one company's code became embedded into numerous products. The software library was created around 1997 and had been implemented by many manufacturers of online devices.

Description

[edit]

Ripple20 is a set of 19 vulnerabilities discovered in 2020 in a software library developed by the Cincinnati-based[1] company Treck Inc., which implemented a TCP/IP stack.[2][3][4]

History

[edit]

The first release of Treck's library was around 1997.[1] Treck had also worked with Elmic Systems, which created a fork of the library when the companies ended their collaboration.[5] In September 2019, JSOF researchers Moshe Kol, Ariel Schön and Shlomi Oberman 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.[5] The disclosure of the vulnerabilities was made in June 2020.[6][7][8][9] 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.[2][10] It is difficult to identify all affected devices, because manufacturers may not realize that the library was used in one of their components.[11]

References

[edit]
  1. 1 2 Cimpanu, Catalin (2018-08-21). "Ripple20 vulnerabilities will haunt the IoT landscape for years to come". ZDNet. Retrieved 2020-07-02.
  2. 1 2 Greenberg, Andy (2020-06-16). "Ripple20 Bugs Put Hundreds of Millions of IoT Devices at Risk". WIRED. Retrieved 2020-07-02.
  3. Coble, Sarah (2020-09-10). "Ripple20 a Major Threat". Infosecurity Magazine. Retrieved 2024-06-20.
  4. "How to mitigate Ripple20 vulnerability risks". CybersecAsia. 2020-09-15. Retrieved 2024-06-20.
  5. 1 2 "disclosure". jsof-tech.com. Retrieved 2020-07-02.
  6. "Ripple20 Threatens Increasingly Connected Medical". Darkreading.com. Retrieved 2020-07-02.
  7. "This Week In Security: Bitdefender, Ripple20, Starbucks, And Pwned Passwords". Hackaday. 2020-06-26. Retrieved 2020-07-02.
  8. "List of Ripple20 vulnerability advisories, patches, and updates". Bleepingcomputer.com. 2020-06-25. Retrieved 2020-07-02.
  9. "Multiple Vulnerabilities in Treck IP Stack Affecting Cisco Products: June 2020". Tools.cisco.com. 2020-06-16. Retrieved 2020-07-02.
  10. "Overview". jsof-tech.com. Retrieved 2020-07-02.
  11. Gold, Jon. "Ripple20 TCP/IP flaws can be patched but still threaten IoT devices". Network World. Retrieved 2020-07-02.
[edit]