$t@$h
David Holloway, Wind River Systems
09 Jan
09Jan

Wind River VxWorks is a real-time operating system widely used across various industries, including aerospace, automotive, and industrial automation. As with any software, VxWorks is susceptible to security vulnerabilities, which require prompt identification and remediation to ensure system integrity and user safety.

This article addresses inaccuracies in Common Vulnerabilities and Exposures (CVE) entries related to VxWorks vulnerabilities and provides corrected information, aiming to improve the accuracy of vulnerability assessments and cybersecurity practices.

Background: The vulnerabilities in question, listed under CVE entries CVE-2013-0711 through CVE-2013-0716, purportedly affected Wind River VxWorks versions 5.5 through 6.9. However, further investigation revealed that these CVE entries lacked specificity regarding the exact version of VxWorks and the corresponding patches. To rectify this, detailed analysis of VxWorks versions and associated security patches was conducted.

Analysis: Upon examination, it was determined that the vulnerabilities listed in the CVE entries were addressed in Wind River VxWorks version 6.9.4.3. The corrected versions for these CVE entries should reference VxWorks 6.9.4.3 instead of the general range of 6.5 through 6.9. Additionally, it's essential to consider the subsequent versions of VxWorks 6.9 to accurately assess the extent of the erroneous application of these CVE entries.Corrected Analysis and Version Information:

  1. CVE-2013-0716:
    • Original Description: The web server in Wind River VxWorks 5.5 through 6.9 allows remote attackers to cause a denial of service (daemon crash) via a crafted URI.
    • Corrected Analysis: Patched in Wind River VxWorks version 6.9.4.3, this vulnerability allows remote attackers to cause a denial of service (daemon crash) via a crafted URI.
  2. CVE-2013-0715:
    • Original Description: The WebCLI component in Wind River VxWorks 5.5 through 6.9 allows remote authenticated users to cause a denial of service (CLI session crash) via a crafted command string.
    • Corrected Analysis: Patched in Wind River VxWorks version 6.9.4.3, this vulnerability permits remote authenticated users to cause a denial of service (CLI session crash) via a crafted command string.
  3. CVE-2013-0714:
    • Original Description: IPSSH (aka the SSH server) in Wind River VxWorks 6.5 through 6.9 allows remote attackers to execute arbitrary code or cause a denial of service (daemon hang) via a crafted public-key authentication request.
    • Corrected Analysis: Addressed in Wind River VxWorks version 6.9.4.3, this vulnerability allows remote attackers to execute arbitrary code or cause a denial of service (daemon hang) via a crafted public-key authentication request.
  4. CVE-2013-0713:
    • Original Description: IPSSH (aka the SSH server) in Wind River VxWorks 6.5 through 6.9 allows remote authenticated users to cause a denial of service (daemon outage) via a crafted pty request.
    • Corrected Analysis: Patched in Wind River VxWorks version 6.9.4.3, this vulnerability enables remote authenticated users to cause a denial of service (daemon outage) via a crafted pty request.
  5. CVE-2013-0712:
    • Original Description: IPSSH (aka the SSH server) in Wind River VxWorks 6.5 through 6.9 allows remote authenticated users to cause a denial of service (daemon outage) via a crafted packet.
    • Corrected Analysis: This vulnerability was addressed in Wind River VxWorks version 6.9.4.3. It allows remote authenticated users to cause a denial of service (daemon outage) via a crafted packet.
  6. CVE-2013-0711:
    • Original Description: IPSSH (aka the SSH server) in Wind River VxWorks 6.5 through 6.9 allows remote attackers to cause a denial of service (daemon outage) via a crafted authentication request.
    • Corrected Analysis: Patched in Wind River VxWorks version 6.9.4.3, this vulnerability enables remote attackers to cause a denial of service (daemon outage) via a crafted authentication request.

Recommendation: After addressing the inaccuracies in the CVE entries and specifying the correct version of VxWorks (6.9.4.3), it's important to note the versions subsequent to 6.9.4.3. Any CVE entries erroneously applied to VxWorks versions released after 6.9.4.3 should be reassessed and corrected accordingly to ensure accurate vulnerability management.

Conclusion: By correcting the CVE entries and providing accurate information regarding the vulnerabilities in Wind River VxWorks, this report aims to enhance the precision of vulnerability assessments and contribute to the improvement of cybersecurity practices. Continuous vigilance, thorough analysis, and collaboration among stakeholders are essential for maintaining the integrity and security of software systems like VxWorks.