dbcve.org
VxworksOperating system · Windriver

CVE-2019-12261

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.7 though 6.9 and vx7 has a Buffer Overflow in the TCP component (issue 3 of 4). This is an IPNET security vulnerability: TCP Urgent Pointer state confusion during connect() to a remote host.

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 · high confidence

Buffer overflow vulnerability in the TCP/IP stack (IPNET) of Wind River VxWorks 6.7-6.9 and vx7 involving TCP Urgent Pointer state confusion during connect() to a remote host, allowing remote code execution.

MitigationApply vendor patches if available; otherwise, implement network segmentation and firewall rules to restrict unauthorized remote connections to affected systems.

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 system operating system
    Run 'uname -a' or check system documentation to determine if the device runs Wind River VxWorks, or identify if the device is a Sonicwall, Siemens, or NetApp product
    Affected if The system runs VxWorks, Sonicwall Sonicos, Siemens firmware, or Netapp E Series and matches the affected version ranges
  2. Check VxWorks version
    Consult system firmware version or run 'version' command if available, or check the VxWorks kernel version via 'sysVrio' or vendor management interface
    Affected if Version is >= 6.5 and < 6.9.4.12, or exactly version 7.0
  3. Check Sonicwall Sonicos version
    Access Sonicwall management interface or run 'show version' via CLI
    Affected if Version falls within any of the affected ranges: 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, or 6.5.3.0-6.5.3.3
  4. Check Siemens device firmware version
    Access device web interface or CLI and check firmware version under system information or about section
    Affected if Siprotec 5 firmware < 7.59 or < 7.91, Power Meter 9410 firmware < 2.2.1, Power Meter 9810 any version, Ruggedcom Win7000/Win7018 firmware < bs5.2.461.17
  5. Check NetApp E Series Santricity OS version
    Access NetApp SANtricity web interface or run 'sysctl -a' or check controller firmware version via management CLI
    Affected if Version is >= 8.00 and <= 8.40.50.00
  6. Verify TCP networking is in use
    Confirm the device has IP networking enabled and accepts TCP connections - check network interface status with 'ifconfig' or 'ip addr'
    Affected if TCP/IP networking stack is active and the device can accept remote connections

The environment is affected if it runs any of the identified products (VxWorks, Sonicwall Sonicos, Siemens devices, or NetApp E Series) within the specific version ranges listed, and has TCP networking enabled.

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 patches if available; otherwise, implement network segmentation and firewall rules to restrict unauthorized remote connections to affected systems.

Recommended fix Moderate confidence

VxWorks: upgrade to >= 6.9.4.12 or VxWorks 7 latest; Other products: upgrade to vendor-specified fixed version (contact vendor for specific release)

  1. 1. Identify the specific affected product and version in your environment from the list: VxWorks, Sonicos, Siprotec 5 Firmware, E Series Santricity Os Controller, Power Meter 9410/9810, or Ruggedcom Win7000/Win7018
  2. 2. For VxWorks: Upgrade to version 6.9.4.12 or later, or migrate to VxWorks 7 with the latest available service pack that includes the IPNET security fix
  3. 3. For SonicWall SonicOS: Apply the specific patch version as indicated in the SonicWall PSIRT advisory (psirt.global.sonicwall.com) for your version range
  4. 4. For Siemens products (Siprotec, Power Meter, Ruggedcom): Contact Siemens ProductCERT for the specific fixed firmware version (refer to cert-portal.siemens.com)
  5. 5. For NetApp E Series Santricity Os Controller: Apply the update as specified in security.netapp.com advisory
  6. 6. Verify the fix by confirming the TCP Urgent Pointer handling no longer exhibits the vulnerability
  7. 7. Test the update in a non-production environment before deploying to production systems
Caveat Upgrading embedded firmware may require validation of existing configurations and compatibility with dependent systems; some legacy functionality may be affected

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

Fix this in Vxworks Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing20.0 h
  • Review / QA8.0 h
64.0 hours of engineering $11,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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