dbcve.org
VxworksOperating system · Windriver

CVE-2019-12264

HIGH · 7.1 CVSS v3.1 Published 2019-08-05
Fix available
A fix is available. Upgrade to after 07.5.01 or later.
See remediation →
76/100
Remediation priority · High
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, 6.7, 6.8, 6.9.3, 6.9.4, and Vx7 has Incorrect Access Control in IPv4 assignment by the ipdhcpc DHCP client component.

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

Incorrect Access Control vulnerability in the ipdhcpc DHCP client component of Wind River VxWorks versions 6.6, 6.7, 6.8, 6.9.3, 6.9.4, and Vx7 allows improper IPv4 address assignment, likely enabling unauthorized network configuration changes.

MitigationImplement network segmentation and access control lists to restrict DHCP traffic to trusted sources; review and restrict physical/network access to the DHCP client interface.

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.6= 6.7= 6.8= 6.9.3= 6.9.4= 7.0
Hirschmann HiosOperating system
Affected:<= 07.0.07<= 07.5.01<= 07.2.04<= 05.3.06
Garrettcom Magnum Dx940e FirmwareOperating system
Affected:<= 1.0.1_y7
Ruggedcom Win7000 FirmwareOperating system
Affected:< bs5.2.461.17
Ruggedcom Win7018 FirmwareOperating system
Affected:< bs5.2.461.17
Ruggedcom Win7025 FirmwareOperating system
Affected:< bs5.2.461.17
Ruggedcom Win7200 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 VxWorks version
    Check the system version through the VxWorks boot banner, /version file, or via the VxWorks kernel shell command 'version'. For embedded devices, this information may also be available via SNMP, web interface, or console boot messages.
    Affected if The version matches 6.6, 6.7, 6.8, 6.9.3, 6.9.4, or 7.0 exactly, or the device firmware matches any of the affected Hirschmann, Garrettcom, or Siemens Ruggedcom versions listed.
  2. Determine if the ipdhcpc DHCP client component is present
    Check if the ipdhcpc process or service is running on the system. On VxWorks systems, this can be verified through the kernel shell using 'iosDrvShow' to list I/O drivers, or by checking for DHCP client functionality in the network stack configuration. For embedded devices, this may be observable through the device's network settings interface.
    Affected if The ipdhcpc DHCP client component is loaded and active on the system.
  3. Verify DHCP is enabled for network interface configuration
    Examine the network interface configuration to determine if DHCP is being used for IPv4 address assignment. Check the network startup scripts, ifconfig output, or the device's web management interface for DHCP client status on active network interfaces.
    Affected if DHCP client is enabled and the system is obtaining IPv4 addresses via DHCP on one or more network interfaces.
  4. Check for Belden Hirschmann device firmware version
    Access the Hirschmann device through its web interface, CLI, or SNMP and retrieve the firmware version information. Compare against the affected versions: HIOS <= 07.0.07, <= 07.5.01, <= 07.2.04, or <= 05.3.06.
    Affected if The device is a Belden Hirschmann product running any of the affected HIOS versions.
  5. Check for Siemens Ruggedcom device firmware version
    Access the Ruggedcom device through its web interface or CLI and retrieve the firmware version. Compare against the affected versions: Win7000, Win7018, Win7025, or Win7200 with firmware versions prior to bs5.2.461.17.
    Affected if The device is a Siemens Ruggedcom Win7000/7018/7025/7200 running firmware version earlier than bs5.2.461.17.

Your environment is affected if you are running any VxWorks version 6.6 through 7.0, or any of the specific Belden Hirschmann or Siemens Ruggedcom firmware versions listed, AND the ipdhcpc DHCP client is enabled and actively assigning IPv4 addresses to network interfaces.

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 a release after 07.5.01
Interim mitigation

Implement network segmentation and access control lists to restrict DHCP traffic to trusted sources; review and restrict physical/network access to the DHCP client interface.

Fix this in Vxworks Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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