Security readout for executives and security teams
Plain-English summary
This CVE affects CODESYS V3 Runtime Toolkit for VxWorks versions V3.5.8.0 through before V3.5.17.10. The public bundle describes improper handling of exceptional conditions but does not provide business impact, CVSS, or exploit details. Treat it as an industrial-control exposure requiring inventory and vendor confirmation.
Executive priority
Prioritize discovery and vendor confirmation, especially for production control environments. The available evidence is too incomplete to justify emergency action by itself, but affected industrial runtime components can carry operational risk and may require planned maintenance coordination.
Technical view
The record identifies improper handling of exceptional conditions in CODESYS V3 Runtime Toolkit for VxWorks before V3.5.17.10, starting at V3.5.8.0. No CWE, CVSS vector, attack preconditions, or affected CPEs are supplied in the bundle. The exact failure mode and security consequence are not evidenced here.
Likely exposure
Exposure is most likely in industrial devices or deployments using CODESYS V3 Runtime Toolkit for VxWorks in the stated version range. Because the bundle lists vendor and product metadata as n/a, confirm applicability through CODESYS, OEM device documentation, and runtime version inventories.
Exploitation context
The bundle does not cite active exploitation, exploit availability, or CISA KEV listing. KEV is false. Do not assume exploitation in the wild from these sources alone.
Researcher notes
Public data is sparse: no CVSS, CWE, exploit notes, or detailed impact statement are provided in the bundle. The only concrete technical boundary is CODESYS V3 Runtime Toolkit for VxWorks from V3.5.8.0 before V3.5.17.10.
Mitigation direction
- Identify VxWorks devices using CODESYS V3 Runtime Toolkit.
- Check whether runtime versions are V3.5.8.0 through before V3.5.17.10.
- Review the linked CODESYS advisory or vendor portal guidance.
- Upgrade to V3.5.17.10 or later only when vendor guidance confirms suitability.
- Coordinate remediation with the OEM for embedded industrial devices.
Validation and detection
- Collect runtime version evidence from asset inventory or vendor tools.
- Confirm whether VxWorks is the runtime operating environment.
- Map affected devices to OEM model and firmware release notes.
- Verify remediation status against CODESYS or OEM advisory language.
- Document compensating controls if upgrades require maintenance windows.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-33486 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://customers.codesys.com/index.php?eID=dumpFile&t=f&f=14806&token=637e12e86301b83beac1653bd88da3aa5aa3f51b&download=CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.