The Great Global Patch: VxWorks Flaws Set to Compromise Millions of Devices
While VxWorks isn't exactly a household name to the average consumer, this software product inevitably benefits many people just like you and me, each and every day. As the world's most popular real-time operating system (RTOS), it is the workhorse we (by proxy) rely on to power enterprise networking and firewalls, aerospace interfaces, industrial equipment, and even some medical devices, just to name a few applications of its widespread use.
And now, we are faced with the possibility that hundreds of millions, if not billions, of these devices, are now compromised with at least eleven vulnerabilities. Wind River's Chief Security Architect, Arlen Baker, has disputed the number in an article from SearchSecurity, revealing the exact scope is unconfirmed and not believed to be that high. Despite this, we already know that data breaches and attacks happen all the time, but this is next-level: the confirmed flaws are relatively easy to exploit, with many opening the door and allowing attackers to control devices remotely through the transmission of network packets.
Wind River has, of course, released a series of fixes and patches to affected customers and associates. The problem lies in the sheer number of devices requiring the patch update - much like Thanos ending the world with a click of his fingers, it is inevitable that many devices will be left unpatched, and therefore vulnerable, for a long time.
Security firm Armis was behind this mammoth discovery, dubbing their findings URGENT/11. They've identified it as serious, undoubtedly due to the ease of attack from multiple vectors and the potential for extensive infection. The creation and deployment of a worm in software powering everything from MRI scanners and VOIP products, to train networks and traffic lights, is entirely possible.
Is it time to panic?
As someone who has made security awareness a critical mission in their life, I see a lot of day-to-day potential security issues. I'd spend most of my day in hysterics if I allowed myself to panic too much (after all, I'd rather get to the business of trying to educate and help fix the bugs!). However, the scope of the URGENT/11 finding is pretty scary. Of the eleven vulnerabilities found, six are considered critical. As The Hacker News identifies, these flaws have existed in devices running VxWorks since version 6.5 (excluding versions designed for certification, including VxWorks 653 and VxWorks Cert Edition), meaning some vital technology has been under threat of device takeover attacks for over a decade now. Not every device is vulnerable to all eleven flaws (and some can only be exploited if the attacker is on the same LAB subnet), but even a mediocre hacker only needs one little window of opportunity.
It is important to note that Wind River has acted quickly and provided detailed advice on mitigating the issues, as has Armis. And, the VxWorks RTOS is so widely adopted because it is so reliable and scores highly for software safety regulations - typically, bug bounty hunters don't bother with it too much. However, security firms and Wind River can only do so much in solving the problem... it is in the hands of the end-user to download patches, heed security advice and fortify their own devices, and that's where it gets tricky.
Perhaps we don't need to panic just yet, but it could take a village to wrestle this beast into submission.
The URGENT/11 vulnerabilities explained
At this point, any device connected to the compromised VxWorks TCP/IP IPnet stack since version 6.5 could be affected by at least one of the URGENT/11. (For a full list of CVEs from Wind River, see here).
Mostly, these flaws allow for remote code execution (RCE) and Denial of Service attacks, with a couple leading to information exposure and business logic issues as well. The remote code execution is a particularly sensitive issue in this instance, as an attacker can assume control of a device with no end-user interaction. Nobody has to accidentally click on anything suspicious, download anything or input their details... it renders VxWorks devices highly "wormable" and the attack to take on an automated life of its own. Remember EternalBlue's WannaCry worm? URGENT/11 has a similar, yet more devastating potential to give us a global headache.
What can we do about it?
Well, at the time of writing, the consequences of URGENT/11 remain unknown. Media has made the industry aware, and Wind River is clearly providing support to those affected. The coming months will reveal if any attackers choose to exploit these known flaws in any meaningful way, but in the meantime, the obvious solution is to heed the plethora of advice and patch any relevant devices in your orbit.
Long-term, it remains the same mission: everyone needs to do better when it comes to software security. The URGENT/11 CVEs are generally, worryingly simple back doors to walk through, and the fact they remained undiscovered for many years is a testament to overall industry concern and awareness being quite low.
Every developer has the chance to do their part, and they need the support to learn how to secure code from the beginning of production. The influential teams around them, everyone from AppSec to the C-suite, can ensure a positive security culture thrives at every software touchpoint within the business.
Want to test your own security awareness? Our gamified platform can give you real code challenges similar to some of those discovered in URGENT/11. Check them out and see how you fare:
- Heap overflow in DHCP Offer/ACK parsing in ipdhcpc (CVE-2019-12257)
Memory Corruption - Heap Overflow - TCP connection DoS via malformed TCP options (CVE-2019-12258)
Insufficient Transport Layer Protection - Unprotected Transport of Sensitive Information - Logical flaw in IPv4 assignment by the ipdhcpc DHCP client (CVE-2019-12264)
Business Logic Flaws - DoS via NULL dereference in IGMP parsing (CVE-2019-12259)
Memory Corruption - Null Dereference - IGMP Information leak via IGMPv3 specific membership report (CVE-2019-12265)
Information Exposure - Sensitive Data Exposure
While VxWorks isn't a household name to the average consumer, this software product benefits many people just like you and me, each and every day. And now, we are faced with the possibility that hundreds of millions of VxWorks-powered devices are now compromised.
Chief Executive Officer, Chairman, and Co-Founder
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
Book a demo
Chief Executive Officer, Chairman, and Co-Founder
Pieter Danhieux is a globally recognized security expert, with over 12 years experience as a security consultant and 8 years as a Principal Instructor for SANS teaching offensive techniques on how to target and assess organizations, systems and individuals for security weaknesses. In 2016, he was recognized as one of the Coolest Tech people in Australia (Business Insider), awarded Cyber Security Professional of the Year (AISA - Australian Information Security Association) and holds GSE, CISSP, GCIH, GCFA, GSEC, GPEN, GWAPT, GCIA certifications.
While VxWorks isn't exactly a household name to the average consumer, this software product inevitably benefits many people just like you and me, each and every day. As the world's most popular real-time operating system (RTOS), it is the workhorse we (by proxy) rely on to power enterprise networking and firewalls, aerospace interfaces, industrial equipment, and even some medical devices, just to name a few applications of its widespread use.
And now, we are faced with the possibility that hundreds of millions, if not billions, of these devices, are now compromised with at least eleven vulnerabilities. Wind River's Chief Security Architect, Arlen Baker, has disputed the number in an article from SearchSecurity, revealing the exact scope is unconfirmed and not believed to be that high. Despite this, we already know that data breaches and attacks happen all the time, but this is next-level: the confirmed flaws are relatively easy to exploit, with many opening the door and allowing attackers to control devices remotely through the transmission of network packets.
Wind River has, of course, released a series of fixes and patches to affected customers and associates. The problem lies in the sheer number of devices requiring the patch update - much like Thanos ending the world with a click of his fingers, it is inevitable that many devices will be left unpatched, and therefore vulnerable, for a long time.
Security firm Armis was behind this mammoth discovery, dubbing their findings URGENT/11. They've identified it as serious, undoubtedly due to the ease of attack from multiple vectors and the potential for extensive infection. The creation and deployment of a worm in software powering everything from MRI scanners and VOIP products, to train networks and traffic lights, is entirely possible.
Is it time to panic?
As someone who has made security awareness a critical mission in their life, I see a lot of day-to-day potential security issues. I'd spend most of my day in hysterics if I allowed myself to panic too much (after all, I'd rather get to the business of trying to educate and help fix the bugs!). However, the scope of the URGENT/11 finding is pretty scary. Of the eleven vulnerabilities found, six are considered critical. As The Hacker News identifies, these flaws have existed in devices running VxWorks since version 6.5 (excluding versions designed for certification, including VxWorks 653 and VxWorks Cert Edition), meaning some vital technology has been under threat of device takeover attacks for over a decade now. Not every device is vulnerable to all eleven flaws (and some can only be exploited if the attacker is on the same LAB subnet), but even a mediocre hacker only needs one little window of opportunity.
It is important to note that Wind River has acted quickly and provided detailed advice on mitigating the issues, as has Armis. And, the VxWorks RTOS is so widely adopted because it is so reliable and scores highly for software safety regulations - typically, bug bounty hunters don't bother with it too much. However, security firms and Wind River can only do so much in solving the problem... it is in the hands of the end-user to download patches, heed security advice and fortify their own devices, and that's where it gets tricky.
Perhaps we don't need to panic just yet, but it could take a village to wrestle this beast into submission.
The URGENT/11 vulnerabilities explained
At this point, any device connected to the compromised VxWorks TCP/IP IPnet stack since version 6.5 could be affected by at least one of the URGENT/11. (For a full list of CVEs from Wind River, see here).
Mostly, these flaws allow for remote code execution (RCE) and Denial of Service attacks, with a couple leading to information exposure and business logic issues as well. The remote code execution is a particularly sensitive issue in this instance, as an attacker can assume control of a device with no end-user interaction. Nobody has to accidentally click on anything suspicious, download anything or input their details... it renders VxWorks devices highly "wormable" and the attack to take on an automated life of its own. Remember EternalBlue's WannaCry worm? URGENT/11 has a similar, yet more devastating potential to give us a global headache.
What can we do about it?
Well, at the time of writing, the consequences of URGENT/11 remain unknown. Media has made the industry aware, and Wind River is clearly providing support to those affected. The coming months will reveal if any attackers choose to exploit these known flaws in any meaningful way, but in the meantime, the obvious solution is to heed the plethora of advice and patch any relevant devices in your orbit.
Long-term, it remains the same mission: everyone needs to do better when it comes to software security. The URGENT/11 CVEs are generally, worryingly simple back doors to walk through, and the fact they remained undiscovered for many years is a testament to overall industry concern and awareness being quite low.
Every developer has the chance to do their part, and they need the support to learn how to secure code from the beginning of production. The influential teams around them, everyone from AppSec to the C-suite, can ensure a positive security culture thrives at every software touchpoint within the business.
Want to test your own security awareness? Our gamified platform can give you real code challenges similar to some of those discovered in URGENT/11. Check them out and see how you fare:
- Heap overflow in DHCP Offer/ACK parsing in ipdhcpc (CVE-2019-12257)
Memory Corruption - Heap Overflow - TCP connection DoS via malformed TCP options (CVE-2019-12258)
Insufficient Transport Layer Protection - Unprotected Transport of Sensitive Information - Logical flaw in IPv4 assignment by the ipdhcpc DHCP client (CVE-2019-12264)
Business Logic Flaws - DoS via NULL dereference in IGMP parsing (CVE-2019-12259)
Memory Corruption - Null Dereference - IGMP Information leak via IGMPv3 specific membership report (CVE-2019-12265)
Information Exposure - Sensitive Data Exposure
While VxWorks isn't exactly a household name to the average consumer, this software product inevitably benefits many people just like you and me, each and every day. As the world's most popular real-time operating system (RTOS), it is the workhorse we (by proxy) rely on to power enterprise networking and firewalls, aerospace interfaces, industrial equipment, and even some medical devices, just to name a few applications of its widespread use.
And now, we are faced with the possibility that hundreds of millions, if not billions, of these devices, are now compromised with at least eleven vulnerabilities. Wind River's Chief Security Architect, Arlen Baker, has disputed the number in an article from SearchSecurity, revealing the exact scope is unconfirmed and not believed to be that high. Despite this, we already know that data breaches and attacks happen all the time, but this is next-level: the confirmed flaws are relatively easy to exploit, with many opening the door and allowing attackers to control devices remotely through the transmission of network packets.
Wind River has, of course, released a series of fixes and patches to affected customers and associates. The problem lies in the sheer number of devices requiring the patch update - much like Thanos ending the world with a click of his fingers, it is inevitable that many devices will be left unpatched, and therefore vulnerable, for a long time.
Security firm Armis was behind this mammoth discovery, dubbing their findings URGENT/11. They've identified it as serious, undoubtedly due to the ease of attack from multiple vectors and the potential for extensive infection. The creation and deployment of a worm in software powering everything from MRI scanners and VOIP products, to train networks and traffic lights, is entirely possible.
Is it time to panic?
As someone who has made security awareness a critical mission in their life, I see a lot of day-to-day potential security issues. I'd spend most of my day in hysterics if I allowed myself to panic too much (after all, I'd rather get to the business of trying to educate and help fix the bugs!). However, the scope of the URGENT/11 finding is pretty scary. Of the eleven vulnerabilities found, six are considered critical. As The Hacker News identifies, these flaws have existed in devices running VxWorks since version 6.5 (excluding versions designed for certification, including VxWorks 653 and VxWorks Cert Edition), meaning some vital technology has been under threat of device takeover attacks for over a decade now. Not every device is vulnerable to all eleven flaws (and some can only be exploited if the attacker is on the same LAB subnet), but even a mediocre hacker only needs one little window of opportunity.
It is important to note that Wind River has acted quickly and provided detailed advice on mitigating the issues, as has Armis. And, the VxWorks RTOS is so widely adopted because it is so reliable and scores highly for software safety regulations - typically, bug bounty hunters don't bother with it too much. However, security firms and Wind River can only do so much in solving the problem... it is in the hands of the end-user to download patches, heed security advice and fortify their own devices, and that's where it gets tricky.
Perhaps we don't need to panic just yet, but it could take a village to wrestle this beast into submission.
The URGENT/11 vulnerabilities explained
At this point, any device connected to the compromised VxWorks TCP/IP IPnet stack since version 6.5 could be affected by at least one of the URGENT/11. (For a full list of CVEs from Wind River, see here).
Mostly, these flaws allow for remote code execution (RCE) and Denial of Service attacks, with a couple leading to information exposure and business logic issues as well. The remote code execution is a particularly sensitive issue in this instance, as an attacker can assume control of a device with no end-user interaction. Nobody has to accidentally click on anything suspicious, download anything or input their details... it renders VxWorks devices highly "wormable" and the attack to take on an automated life of its own. Remember EternalBlue's WannaCry worm? URGENT/11 has a similar, yet more devastating potential to give us a global headache.
What can we do about it?
Well, at the time of writing, the consequences of URGENT/11 remain unknown. Media has made the industry aware, and Wind River is clearly providing support to those affected. The coming months will reveal if any attackers choose to exploit these known flaws in any meaningful way, but in the meantime, the obvious solution is to heed the plethora of advice and patch any relevant devices in your orbit.
Long-term, it remains the same mission: everyone needs to do better when it comes to software security. The URGENT/11 CVEs are generally, worryingly simple back doors to walk through, and the fact they remained undiscovered for many years is a testament to overall industry concern and awareness being quite low.
Every developer has the chance to do their part, and they need the support to learn how to secure code from the beginning of production. The influential teams around them, everyone from AppSec to the C-suite, can ensure a positive security culture thrives at every software touchpoint within the business.
Want to test your own security awareness? Our gamified platform can give you real code challenges similar to some of those discovered in URGENT/11. Check them out and see how you fare:
- Heap overflow in DHCP Offer/ACK parsing in ipdhcpc (CVE-2019-12257)
Memory Corruption - Heap Overflow - TCP connection DoS via malformed TCP options (CVE-2019-12258)
Insufficient Transport Layer Protection - Unprotected Transport of Sensitive Information - Logical flaw in IPv4 assignment by the ipdhcpc DHCP client (CVE-2019-12264)
Business Logic Flaws - DoS via NULL dereference in IGMP parsing (CVE-2019-12259)
Memory Corruption - Null Dereference - IGMP Information leak via IGMPv3 specific membership report (CVE-2019-12265)
Information Exposure - Sensitive Data Exposure
Click on the link below and download the PDF of this resource.
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
View reportBook a demo
Chief Executive Officer, Chairman, and Co-Founder
Pieter Danhieux is a globally recognized security expert, with over 12 years experience as a security consultant and 8 years as a Principal Instructor for SANS teaching offensive techniques on how to target and assess organizations, systems and individuals for security weaknesses. In 2016, he was recognized as one of the Coolest Tech people in Australia (Business Insider), awarded Cyber Security Professional of the Year (AISA - Australian Information Security Association) and holds GSE, CISSP, GCIH, GCFA, GSEC, GPEN, GWAPT, GCIA certifications.
While VxWorks isn't exactly a household name to the average consumer, this software product inevitably benefits many people just like you and me, each and every day. As the world's most popular real-time operating system (RTOS), it is the workhorse we (by proxy) rely on to power enterprise networking and firewalls, aerospace interfaces, industrial equipment, and even some medical devices, just to name a few applications of its widespread use.
And now, we are faced with the possibility that hundreds of millions, if not billions, of these devices, are now compromised with at least eleven vulnerabilities. Wind River's Chief Security Architect, Arlen Baker, has disputed the number in an article from SearchSecurity, revealing the exact scope is unconfirmed and not believed to be that high. Despite this, we already know that data breaches and attacks happen all the time, but this is next-level: the confirmed flaws are relatively easy to exploit, with many opening the door and allowing attackers to control devices remotely through the transmission of network packets.
Wind River has, of course, released a series of fixes and patches to affected customers and associates. The problem lies in the sheer number of devices requiring the patch update - much like Thanos ending the world with a click of his fingers, it is inevitable that many devices will be left unpatched, and therefore vulnerable, for a long time.
Security firm Armis was behind this mammoth discovery, dubbing their findings URGENT/11. They've identified it as serious, undoubtedly due to the ease of attack from multiple vectors and the potential for extensive infection. The creation and deployment of a worm in software powering everything from MRI scanners and VOIP products, to train networks and traffic lights, is entirely possible.
Is it time to panic?
As someone who has made security awareness a critical mission in their life, I see a lot of day-to-day potential security issues. I'd spend most of my day in hysterics if I allowed myself to panic too much (after all, I'd rather get to the business of trying to educate and help fix the bugs!). However, the scope of the URGENT/11 finding is pretty scary. Of the eleven vulnerabilities found, six are considered critical. As The Hacker News identifies, these flaws have existed in devices running VxWorks since version 6.5 (excluding versions designed for certification, including VxWorks 653 and VxWorks Cert Edition), meaning some vital technology has been under threat of device takeover attacks for over a decade now. Not every device is vulnerable to all eleven flaws (and some can only be exploited if the attacker is on the same LAB subnet), but even a mediocre hacker only needs one little window of opportunity.
It is important to note that Wind River has acted quickly and provided detailed advice on mitigating the issues, as has Armis. And, the VxWorks RTOS is so widely adopted because it is so reliable and scores highly for software safety regulations - typically, bug bounty hunters don't bother with it too much. However, security firms and Wind River can only do so much in solving the problem... it is in the hands of the end-user to download patches, heed security advice and fortify their own devices, and that's where it gets tricky.
Perhaps we don't need to panic just yet, but it could take a village to wrestle this beast into submission.
The URGENT/11 vulnerabilities explained
At this point, any device connected to the compromised VxWorks TCP/IP IPnet stack since version 6.5 could be affected by at least one of the URGENT/11. (For a full list of CVEs from Wind River, see here).
Mostly, these flaws allow for remote code execution (RCE) and Denial of Service attacks, with a couple leading to information exposure and business logic issues as well. The remote code execution is a particularly sensitive issue in this instance, as an attacker can assume control of a device with no end-user interaction. Nobody has to accidentally click on anything suspicious, download anything or input their details... it renders VxWorks devices highly "wormable" and the attack to take on an automated life of its own. Remember EternalBlue's WannaCry worm? URGENT/11 has a similar, yet more devastating potential to give us a global headache.
What can we do about it?
Well, at the time of writing, the consequences of URGENT/11 remain unknown. Media has made the industry aware, and Wind River is clearly providing support to those affected. The coming months will reveal if any attackers choose to exploit these known flaws in any meaningful way, but in the meantime, the obvious solution is to heed the plethora of advice and patch any relevant devices in your orbit.
Long-term, it remains the same mission: everyone needs to do better when it comes to software security. The URGENT/11 CVEs are generally, worryingly simple back doors to walk through, and the fact they remained undiscovered for many years is a testament to overall industry concern and awareness being quite low.
Every developer has the chance to do their part, and they need the support to learn how to secure code from the beginning of production. The influential teams around them, everyone from AppSec to the C-suite, can ensure a positive security culture thrives at every software touchpoint within the business.
Want to test your own security awareness? Our gamified platform can give you real code challenges similar to some of those discovered in URGENT/11. Check them out and see how you fare:
- Heap overflow in DHCP Offer/ACK parsing in ipdhcpc (CVE-2019-12257)
Memory Corruption - Heap Overflow - TCP connection DoS via malformed TCP options (CVE-2019-12258)
Insufficient Transport Layer Protection - Unprotected Transport of Sensitive Information - Logical flaw in IPv4 assignment by the ipdhcpc DHCP client (CVE-2019-12264)
Business Logic Flaws - DoS via NULL dereference in IGMP parsing (CVE-2019-12259)
Memory Corruption - Null Dereference - IGMP Information leak via IGMPv3 specific membership report (CVE-2019-12265)
Information Exposure - Sensitive Data Exposure
Table of contents
Chief Executive Officer, Chairman, and Co-Founder
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
Book a demoDownloadResources to get you started
Resources to get you started
10 Key Predictions: Secure Code Warrior on AI & Secure-by-Design’s Influence in 2025
Organizations are facing tough decisions on AI usage to support long-term productivity, sustainability, and security ROI. It’s become clear to us over the last few years that AI will never fully replace the role of the developer. From AI + developer partnerships to the increasing pressures (and confusion) around Secure-by-Design expectations, let’s take a closer look at what we can expect over the next year.
OWASP Top 10 For LLM Applications: What’s New, Changed, and How to Stay Secure
Stay ahead in securing LLM applications with the latest OWASP Top 10 updates. Discover what's new, what’s changed, and how Secure Code Warrior equips you with up-to-date learning resources to mitigate risks in Generative AI.
Trust Score Reveals the Value of Secure-by-Design Upskilling Initiatives
Our research has shown that secure code training works. Trust Score, using an algorithm drawing on more than 20 million learning data points from work by more than 250,000 learners at over 600 organizations, reveals its effectiveness in driving down vulnerabilities and how to make the initiative even more effective.
.png)
Reactive Versus Preventive Security: Prevention Is a Better Cure
The idea of bringing preventive security to legacy code and systems at the same time as newer applications can seem daunting, but a Secure-by-Design approach, enforced by upskilling developers, can apply security best practices to those systems. It’s the best chance many organizations have of improving their security postures.
Developer-driven coding.
Securely.
Contact us today and make software security an intrinsic part of your development process.
