CVE-2022-23937
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 · uneditedIn Wind River VxWorks 6.9 and 7, a specific crafted packet may lead to an out-of-bounds read during an IKE initial exchange scenario.
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 confidenceOut-of-bounds read vulnerability in Wind River VxWorks 6.9 and 7 IKE (Internet Key Exchange) implementation during initial exchange, triggered by specially crafted packets, potentially allowing disclosure of sensitive memory contents.
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= 6.9= 7.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if system runs Wind River VxWorksQuery the system firmware, boot logs, or OS identification for 'VxWorks' branding. On network devices, check the device model and firmware version via SNMP, SSH console, or management interface.Affected if The system is identified as running Wind River VxWorks
-
Confirm VxWorks version is 6.9 or 7.0Check the exact firmware/OS version string. On VxWorks devices, this is often visible in boot messages, in the system info via SNMP OID 1.3.6.1.4.1.674.10892.1, or through the management console command 'version' or 'show version'.Affected if The installed version is exactly 6.9 or exactly 7.0 (note: other versions like 6.9.x or 7.0.0.x beyond base releases may have separate advisories)
-
Verify IKE/IPsec is enabledCheck the VxWorks configuration for IKE daemon or IPsec VPN settings. This may appear in the running config, startup scripts, or management GUI under VPN, IPsec, or IKE settings. Look for processes like 'ikeDaemon' or 'ipsec' in the process list.Affected if IKE is configured or running on the device
The environment is affected if it runs VxWorks version 6.9 or 7.0 AND has IKE/IPsec enabled, as the vulnerability exists only in the IKE implementation during initial exchange processing.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patches when available; meanwhile, mitigate by network isolating affected devices, blocking IKE traffic at perimeter firewalls, or disabling IKE if not required.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23937 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23937 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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