dbcve.org
VxworksOperating system · Windriver

CVE-2019-12260

CRITICAL · 9.8 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 →
100/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 and vx7 has a Buffer Overflow in the TCP component (issue 2 of 4). This is an IPNET security vulnerability: TCP Urgent Pointer state confusion caused by a malformed TCP AO option.

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

A buffer overflow vulnerability in Wind River VxWorks 6.9 and vx7 TCP component allows remote code execution via malformed TCP AO (Authentication Option) causing TCP Urgent Pointer state confusion. The vulnerability stems from improper handling of the TCP urgent pointer when processing a crafted TCP option, leading to memory corruption.

MitigationApply vendor-supplied VxWorks security patches. If no patch is available, implement network segmentation to limit exposure of affected devices and disable TCP AO if not required. Consider upgrading to a supported VxWorks version.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 product and firmware/OS version
    Determine if the system runs Wind River VxWorks, Sonicwall Sonicos, Siemens Siprotec, Siemens Ruggedcom, Siemens Power Meter, or NetApp E-Series. Obtain the exact version number from the device's system information, about page, or CLI command such as 'version', 'show system', or 'get version'.
    Affected if The installed version falls within any of the affected ranges: VxWorks 6.5 to 6.9.4.11 or 7.0; Sonicwall Sonicos versions listed in the advisory; Siemens Siprotec 5 Firmware before 7.59 or 7.91; NetApp E-Series Santricity OS 8.00 to 8.40.50.00; Siemens Power Meter 9410 below 2.2.1; Siemens Power Met
  2. Verify TCP AO feature is in use
    Examine the TCP configuration on the affected device. For VxWorks systems, check if TCP Authentication Option (TCP-AO) is enabled in the network stack configuration or running config. Look for TCP-AO settings in the protocol configuration files or management interface.
    Affected if TCP AO (Authentication Option) is explicitly configured or enabled on the device. The vulnerability requires malformed TCP AO packets to trigger the urgent pointer state confusion.
  3. Check for TCP urgent pointer handling
    Review network packet captures or TCP stack logs for any unusual TCP options processing. On VxWorks, inspect TCP component logs or debugging output related to urgent pointer handling. For network devices, check if the TCP stack processes TCP options with the urgent flag set.
    Affected if The device processes incoming TCP traffic with TCP AO options and urgent pointer fields. The vulnerability is triggered by malformed TCP AO causing confusion in urgent pointer state processing.
  4. Confirm product uses the vulnerable VxWorks TCP stack
    For non-VxWorks branded products (Sonicwall, Siemens, NetApp), verify through product documentation or firmware metadata that the underlying TCP implementation is derived from the vulnerable VxWorks TCP component. Check release notes or security advisories from the specific vendor.
    Affected if The device firmware is based on or includes the vulnerable Wind River VxWorks TCP/IP stack component, regardless of the product brand name.

The environment is affected if the device runs any of the listed product versions AND uses TCP AO (Authentication Option) functionality, since the vulnerability requires malformed TCP AO packets to trigger the buffer overflow via TCP urgent pointer state confusion.

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.

dbcve · scoped
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 VxWorks security patches. If no patch is available, implement network segmentation to limit exposure of affected devices and disable TCP AO if not required. Consider upgrading to a supported VxWorks version.

Recommended fix High confidence

Vendor-specific fixed firmware versions (e.g., VxWorks 6.9.4.12+, Sonicos 6.2.4.4+, Siprotec 5 firmware 7.59+/7.91+, etc.)

  1. 1. Identify the specific affected product and version in your environment from the list: VxWorks (6.5 to <6.9.4.12, or 7.0), SonicWall Sonicos, Siemens Siprotec 5, NetApp E Series Santricity OS Controller, Power Meter 9410/9810, or Ruggedcom Win7000/Win7018
  2. 2. For VxWorks-based systems: Contact Wind River for the specific patch or upgrade to VxWorks 6.9.4.12 or later, or obtain the fixed VxWorks 7.0 release
  3. 3. For Siemens products (Siprotec 5): Obtain firmware version 7.59 or higher (for older hardware) or 7.91 or higher (for newer hardware) from Siemens cert-portal
  4. 4. For SonicWall Sonicos: Obtain firmware version 6.2.4.4 or higher from the SonicWall support portal
  5. 5. For NetApp E Series Santricity OS Controller: Obtain updated firmware from security.netapp.com per their advisory
  6. 6. For Power Meter devices: Contact the vendor (Siemens) for firmware 2.2.1 or higher for model 9410; model 9810 requires vendor contact for remediation
  7. 7. For Ruggedcom Win7000/Win7018: Obtain firmware bs5.2.461.17 or higher from Siemens/Ruggedcom
  8. 8. Test the firmware update in a non-production environment before deployment
Caveat Firmware updates may require system downtime and could have compatibility implications with dependent systems; test thoroughly before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vxworks Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-12260 — 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-12260 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