dbcve.org
VxworksOperating system · Windriver

CVE-2019-12256

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 IPv4 component. There is an IPNET security vulnerability: Stack overflow in the parsing of IPv4 packets’ IP options.

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

Stack-based buffer overflow in Wind River VxWorks IPNET stack when parsing IPv4 packet options. The vulnerability allows remote attackers to overflow the stack via specially crafted IPv4 packets containing malformed IP options, potentially enabling remote code execution.

MitigationApply vendor patches for VxWorks 6.9 and vx7; if patches unavailable, implement network-level filtering of IPv4 packets with unusual option configurations and restrict network exposure of affected devices.

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
E Series Santricity Os ControllerOperating system
Affected:>= 8.00, <= 8.40.50.00
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
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 OS
    Determine the system product: check if it runs Wind River VxWorks, Netapp E Series Santricity, Sonicwall Sonicos, or Siemens device (Siprotec 5, Power Meter 9410/9810, Ruggedcom Win7000/Win7018)
    Affected if The system runs any of the affected products listed in the CVE
  2. Check VxWorks version
    Use system commands or firmware lookup to identify the VxWorks version. Affected versions are >= 6.5 and < 6.9.4.12
    Affected if VxWorks version is 6.5 through 6.9.4.11 inclusive
  3. Check Netapp E Series firmware
    Access Netapp E Series controller management to check Santricity OS version. Affected versions are >= 8.00 and <= 8.40.50.00
    Affected if Santricity OS version is between 8.00 and 8.40.50.00 inclusive
  4. Check Sonicwall Sonicos version
    Access Sonicwall appliance management interface or check firmware to identify Sonicos version. Compare against 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, 6.5.3.0-6.5.3.3
    Affected if Sonicos version matches any of the affected version ranges
  5. Check Siemens firmware version
    Check firmware version on Siemens Siprotec 5, Power Meter 9410, Power Meter 9810, or Ruggedcom Win7000/Win7018. For Siprotec 5: affected if < 7.59 or < 7.91. For Power Meter 9410: affected if < 2.2.1. For Power Meter 9810: all versions affected. For Ruggedcom Win7000/Win7018: affected if < bs5.2.461.17
    Affected if Firmware version is below the fixed version or is any version for Power Meter 9810
  6. Verify IPv4 processing is enabled
    Check if the system has IPv4 packet processing enabled. This is typically always enabled in affected products but confirm that IPNET networking stack is active
    Affected if IPv4 packet processing and IPNET stack are enabled on the system

The system is affected if it runs any of the listed products within their specific vulnerable version ranges and has IPv4 packet processing 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 for VxWorks 6.9 and vx7; if patches unavailable, implement network-level filtering of IPv4 packets with unusual option configurations and restrict network exposure of affected devices.

Recommended fix High confidence

VxWorks 6.9.4.12 or later / VxWorks 7; SonicOS 5.9.0.8, 5.9.1.13, 6.2.3.2, or 6.2.4.4; Siprotec 5 firmware 7.59 or 7.91; Power Meter 9410 firmware 2.2.1; Ruggedcom firmware bs5.2.461.17

  1. 1. Identify the specific product from the affected list (VxWorks, E Series Santricity OS Controller, SonicOS, Siprotec 5, Power Meter 9410/9810, Ruggedcom Win7000/Win7018)
  2. 2. Determine the current firmware/software version installed
  3. 3. For VxWorks: Upgrade to version 6.9.4.12 or later, or migrate to VxWorks 7 if still on vx7
  4. 4. For NetApp E Series Santricity OS Controller: Upgrade to a version higher than 8.40.50.00
  5. 5. For SonicWall SonicOS: Upgrade to version 5.9.0.8, 5.9.1.13, 6.2.3.2, or 6.2.4.4 (depending on branch)
  6. 6. For Siemens Siprotec 5: Upgrade firmware to 7.59 or higher (for certain models) or 7.91 or higher
  7. 7. For Siemens Power Meter 9410: Upgrade firmware to 2.2.1 or later
  8. 8. For Siemens Power Meter 9810: Contact vendor for mitigation guidance as no fix available
Caveat Upgrading embedded firmware may require downtime and could affect dependent systems; verify compatibility with connected systems before upgrading

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 / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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