Editing VxWorks (section)

== TCP vulnerability and CVE patches ==
As of July 2019, a paper published by Armis<ref>{{Cite web|url=https://go.armis.com/hubfs/White-papers/Urgent11%20Technical%20White%20Paper.pdf|title=Urgent/11 Critical Vulnerability|website=Armis|access-date=July 31, 2019|archive-date=August 3, 2019|archive-url=https://web.archive.org/web/20190803101359/https://go.armis.com/hubfs/White-papers/Urgent11%20Technical%20White%20Paper.pdf|url-status=dead}}</ref> exposed 11 critical vulnerabilities, including [[Arbitrary code execution|remote code execution]], [[Denial-of-service attack|denial of service]], information leaks, and logical flaws impacting more than two billion devices using the VxWorks RTOS.<ref>{{Cite web|url=https://www.tenable.com/blog/critical-vulnerabilities-dubbed-urgent11-place-devices-running-vxworks-at-risk-of-rce-attacks|title=Critical Vulnerabilities Dubbed URGENT/11 Place Devices Running VxWorks at Risk of RCE Attacks|date=2019-07-29|website=Tenable®|language=en|access-date=2019-07-31}}</ref> The vulnerability allows attackers to [[Tunneling protocol|tunnel]] into an ''internal'' network using the vulnerability and hack into printers, laptops, and any other connected devices. The vulnerability can bypass firewalls as well.<ref>{{Cite web|url=https://blog.sonicwall.com/en-us/2019/07/wind-river-vxworks-and-urgent-11-patch-now/|title=Wind River VxWorks and URGENT/11: Patch Now|last=Gmuender|first=John|date=2019-07-29|website=SonicWall|language=en-us|access-date=2019-07-31}}</ref>

The system is in use by quite a few [[mission-critical]] products, many of which could not be easily patched.<ref>{{Cite magazine|url=https://www.wired.com/story/vxworks-vulnerabilities-urgent11/|title=An Operating System Bug Exposes 200 Million Critical Devices|last1=Newman|first1=Lily Han|magazine=Wired}}</ref>