dbcve.org
VxworksOperating system · Windriver

CVE-2022-38767

HIGH · 7.5 CVSS v3.1 Published 2022-11-25
Fix available
A fix is available. Upgrade to 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
An issue was discovered in Wind River VxWorks 6.9 and 7, that allows a specifically crafted packet sent by a Radius server, may cause Denial of Service during the IP Radius access procedure.

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

A vulnerability in Wind River VxWorks 6.9 and 7 allows a malicious or compromised RADIUS server to send a specially crafted packet that triggers a denial of service condition during the IP RADIUS access procedure. The flaw exists in the RADIUS authentication handling code, causing the affected system to crash or become unresponsive when processing the malformed packet.

MitigationIsolate RADIUS server infrastructure on trusted network segments, implement packet filtering for RADIUS traffic (UDP ports 1812/1813), and apply any vendor patches when available. If no patch exists, consider implementing redundant authentication infrastructure to maintain availability.

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.4.12= 6.9.4.12= 7.0

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 the installed VxWorks version
    Access the VxWorks system management interface or boot diagnostics to retrieve the OS version number. Look for a version string such as 6.9.x or 7.0.x in the system information or kernel configuration.
    Affected if The version is 6.9 (any version from 6.9 through 6.9.4.12 inclusive) or exactly version 7.0
  2. Confirm RADIUS authentication is configured
    Examine the VxWorks network configuration files or IPsec/IKE settings for RADIUS server definitions. Check for entries specifying RADIUS server IP addresses on UDP ports 1812 or 1813 in the authentication configuration.
    Affected if RADIUS access authentication is enabled and a RADIUS server is configured as an authentication backend
  3. Check for vulnerable RADIUS handling code
    Review the system's authentication subsystem logs or memory dump if available. The vulnerability exists specifically in the RADIUS access procedure handling code during IP RADIUS authentication.
    Affected if The system processes RADIUS authentication requests and uses the affected code path
  4. Verify network exposure of RADIUS service
    Determine if the VxWorks device has network connectivity to untrusted RADIUS server infrastructure. Check firewall rules or access control lists protecting UDP ports 1812 and 1813.
    Affected if The RADIUS client can communicate with a RADIUS server that is on an untrusted or compromised network segment

A system is affected if it runs VxWorks version 6.9 (through 6.9.4.12) or 7.0 AND has RADIUS authentication enabled, allowing a compromised RADIUS server to send malformed packets that crash the device.

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

Isolate RADIUS server infrastructure on trusted network segments, implement packet filtering for RADIUS traffic (UDP ports 1812/1813), and apply any vendor patches when available. If no patch exists, consider implementing redundant authentication infrastructure to maintain availability.

Recommended fix Moderate confidence

VxWorks 6.9.4.13+ or VxWorks 7.x (latest release)

  1. 1. Contact Wind River support (support2.windriver.com) to obtain the specific patch or fixed version for this CVE.
  2. 2. If running VxWorks 6.9.x, upgrade to a version newer than 6.9.4.12 (e.g., 6.9.4.13 or later if available).
  3. 3. If running VxWorks 7.0, upgrade to the latest VxWorks 7.x release or apply the relevant security patch from Wind River.
  4. 4. After upgrading, verify the RADIUS authentication functionality works correctly.
  5. 5. Test that the system no longer crashes when receiving crafted RADIUS packets.
Caveat Check release notes for any API or configuration changes between versions; contact Wind River for migration guidance

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

Fix this in Vxworks Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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