dbcve.org
VxworksOperating system · Windriver

CVE-2019-9865

HIGH · 8.1 CVSS v3.0 Published 2019-05-29
Fix available
A fix is available. Upgrade to 6.9.1 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
When RPC is enabled in Wind River VxWorks 6.9 prior to 6.9.1, a specially crafted RPC request can trigger an integer overflow leading to an out-of-bounds memory copy. It may allow remote attackers to cause a denial of service (crash) or possibly execute arbitrary code.

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

Integer overflow in the RPC handler of Wind River VxWorks 6.9 (when RPC is enabled) allows specially crafted RPC requests to trigger an out-of-bounds memory copy, enabling remote code execution or denial of service.

MitigationUpgrade VxWorks to version 6.9.1 or later; if RPC is not required, disable the RPC service to eliminate the attack surface.

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.9, < 6.9.1= 6.6= 6.7= 6.8

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.0/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 installed VxWorks version
    Retrieve the VxWorks version from the system banner, boot parameters, or by querying the kernel using 'version' command or checking the OS release file. Common paths include /etc/vxworks-release or inspecting boot loader configuration.
    Affected if The version is 6.6, 6.7, 6.8, or >= 6.9 but < 6.9.1 (such as 6.9, 6.9.0.1, 6.9.0.2, etc.)
  2. Confirm RPC service is enabled
    Check if the RPC (Remote Procedure Call) service is active on the system. This may involve examining running processes for 'rpc.' daemons, checking /etc/rc.config for RPC startup scripts, or querying the service status via the VxWorks management interface if available.
    Affected if RPC is enabled and running on the target system

A system is affected if it runs VxWorks version 6.6, 6.7, 6.8, or any 6.9.x version prior to 6.9.1 AND has the RPC service enabled, as the integer overflow only triggers through the RPC handler.

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 6.9.1 or later
Fixed in 6.9.1
Interim mitigation

Upgrade VxWorks to version 6.9.1 or later; if RPC is not required, disable the RPC service to eliminate the attack surface.

Fix this in Vxworks Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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