dbcve.org
VxworksOperating system · Windriver

CVE-2019-12263

HIGH · 8.1 CVSS v3.1 Published 2019-08-09
Fix available
A fix is available. Upgrade to 2.2.1 / 6.9.4.12 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Wind River VxWorks 6.9.4 and vx7 has a Buffer Overflow in the TCP component (issue 4 of 4). There is an IPNET security vulnerability: TCP Urgent Pointer state confusion due to race condition.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

CVE-2019-12263 is a buffer overflow vulnerability in the TCP component of Wind River VxWorks 6.9.4 and vx7 operating systems. The vulnerability stems from a race condition in the IPNET networking stack that causes TCP Urgent Pointer state confusion. This memory corruption issue in the TCP handling can potentially allow remote attackers to execute arbitrary code or cause a denial of service.

MitigationApply vendor-supplied patches from Wind River for VxWorks. If patches are unavailable, implement network segmentation and firewall rules to limit exposure to the TCP protocol attack surface, as this is a network-exploitable vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VxworksOperating system
Affected:>= 6.5, < 6.9.4.12= 7.0
SonicosOperating system
Affected:>= 5.9.0.0, <= 5.9.0.7>= 5.9.1.0., <= 5.9.1.12>= 6.2.0.0, <= 6.2.3.1>= 6.2.4.0, <= 6.2.4.3>= 6.2.5.0, <= 6.2.5.3>= 6.2.6.0, <= 6.2.6.1>= 6.2.7.0, <= 6.2.7.4>= 6.2.9.0, <= 6.2.9.2>= 6.5.0.0, <= 6.5.0.3>= 6.5.1.0, <= 6.5.1.4>= 6.5.2.0, <= 6.5.2.3>= 6.5.3.0, <= 6.5.3.3
Siprotec 5 FirmwareOperating system
Affected:< 7.59< 7.91
E Series Santricity Os ControllerOperating system
Affected:>= 8.00, <= 8.40.50.00
Power Meter 9410 FirmwareOperating system
Affected:< 2.2.1
Power Meter 9810 FirmwareOperating system
Affected:all versions
Ruggedcom Win7000 FirmwareOperating system
Affected:< bs5.2.461.17
Ruggedcom Win7018 FirmwareOperating system
Affected:< bs5.2.461.17

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the embedded OS or firmware product
    Check system documentation, login banner, or firmware identification. For VxWorks, check the boot prompt or run 'version' command if available. For Sonicwall, check the appliance admin interface under System > Status. For Siemens devices, check the web UI or SNMP sysDescr.
    Affected if The device runs Wind River VxWorks, Sonicwall SoniOS, or Siemens firmware (Siprotec 5, Power Meter 9410/9810, or Ruggedcom Win7000/7018)
  2. Determine the exact version number
    For VxWorks: use the VxWorks shell or check the build manifest. For Sonicwall: navigate to System > Status in the management interface to view the OS version. For Siemens devices: check the firmware version in the device web UI under About or Diagnostics.
    Affected if The version falls within any of the affected ranges: VxWorks >= 6.5 but < 6.9.4.12, or exactly version 7.0; SoniOS in any of the listed version ranges; Siemens Siprotec < 7.59 or < 7.91; Siemens Power Meter 9410 < 2.2.1; Siemens Power Meter 9810 any version; Siemens Ruggedcom Win7000/7018 < bs5.2.46
  3. Verify TCP/IP networking is enabled
    Check the network configuration on the device. For VxWorks: verify ipnet or tcp/ip stack is running via shell command 'ifconfig' or 'netstat -a'. For Sonicwall: ensure the appliance has network interfaces configured and TCP traffic is allowed. For Siemens devices: confirm network adapter is enabled in the configuration.
    Affected if TCP networking stack is active and the device has IP connectivity
  4. Confirm the device is exposed to network attack surface
    Review firewall rules, access lists, and network segmentation. Check if the device TCP ports (any or specifically ports 20-21, 23, 25, 80, 443, etc.) are accessible from untrusted networks. For Sonicwall: verify WAN interface is exposed. For VxWorks devices: check if they are directly connected to the internet or DMZ.
    Affected if The device TCP stack is reachable from external or less-trusted network segments
  5. Check for vendor-specific version commands
    For Sonicwall SoniOS: use the CLI command 'show version' or check via GUI. For Siemens devices: use SNMP GET on sysDescr or check the specific firmware version via the web UI or serial console. For Netapp E Series: check via SANtricity web interface under Support > Storage Array Profile.
    Affected if The product cannot be identified or version cannot be determined, but the device type matches affected vendors

A system is affected if it runs any of the identified products (VxWorks, Sonicwall SoniOS, Siemens firmware, or Netapp E Series) at a version within the specified vulnerable ranges AND has TCP networking enabled and reachable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 2.2.1 / 6.9.4.12 / 7.59 or later
Fixed in 2.2.16.9.4.127.59
Interim mitigation

Apply vendor-supplied patches from Wind River for VxWorks. If patches are unavailable, implement network segmentation and firewall rules to limit exposure to the TCP protocol attack surface, as this is a network-exploitable vulnerability.

Fix this in Vxworks Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-12263 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-12263 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data