dbcve.org
VxworksOperating system · Windriver

CVE-2019-12258

HIGH · 7.5 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 →
84/100
Remediation priority · High
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.6 through vx7 has Session Fixation in the TCP component. This is a IPNET security vulnerability: DoS of TCP connection via malformed TCP 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 · moderate confidence

CVE-2019-12258 is a vulnerability in Wind River VxWorks versions 6.6 through vx7 IPNET networking stack that allows session fixation in the TCP component. Attackers can cause denial of service by sending malformed TCP options that disrupt TCP connections.

MitigationApply vendor patches for VxWorks IPNET; if immediate patching is unavailable, implement network segmentation and ingress filtering to block malformed TCP packets at network boundaries.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 VxWorks IPNET version
    Check system documentation, boot logs, or query the IPNET stack version via vendor-provided CLI or SNMP if available. Look for files or registers that expose the networking stack version.
    Affected if The installed IPNET version is between 6.6 and vx7, or equals 6.5.x, 6.9.x before 6.9.4.12, or exactly 7.0
  2. Check Wind River VxWorks firmware version
    Access the device management interface or check the firmware image metadata. For embedded devices, this is often displayed in the system info page or via 'version' command in console.
    Affected if The VxWorks version is >= 6.5 and < 6.9.4.12, or equals exactly 7.0
  3. Identify Sonicwall SoniOS version
    Log into the Sonicwall management GUI or CLI and navigate to System > Status to view the firmware version. Alternatively, check the firmware file name or release notes.
    Affected if The SoniOS version matches 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 Siprotec 5 firmware version
    Access the device web interface or use the protection engineering tool to view the firmware version under device information or system settings.
    Affected if The firmware version is below 7.59 or below 7.91 (depending on hardware generation)
  5. Verify TCP networking stack is in use
    Confirm that the device uses the IPNET networking component for TCP communications. This may be evident from network configuration, stack banners, or product documentation indicating IPNET usage.
    Affected if The device leverages the VxWorks IPNET stack for TCP handling and the version falls within affected ranges

You are affected if your device runs VxWorks IPNET or a product listed in the affected versions with the IPNET TCP stack enabled, and the installed version falls within the specified vulnerable ranges.

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 patches for VxWorks IPNET; if immediate patching is unavailable, implement network segmentation and ingress filtering to block malformed TCP packets at network boundaries.

Fix this in Vxworks Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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