Security readout for executives and security teams
Plain-English summary
CVE-2020-35198 affects Wind River VxWorks 7. A memory allocation calculation can overflow, causing less memory to be allocated than requested. That can lead to memory corruption in affected systems. The public bundle does not provide CVSS, fixed versions, or affected product details beyond VxWorks 7.
Executive priority
Prioritize discovery over emergency response. The vulnerability can cause memory corruption, but severity, exploit status, and fixed versions are not established in the supplied sources. Organizations with VxWorks 7 in operational or embedded environments should confirm vendor exposure and update paths.
Technical view
The issue is in the VxWorks 7 memory allocator. An integer overflow in calloc() size calculation may produce an undersized allocation relative to requested arguments, creating memory corruption risk. The supplied sources do not describe attack prerequisites, reachable interfaces, exploitability, or specific impacted builds.
Likely exposure
Exposure is most likely in embedded, industrial, network, or appliance environments using Wind River VxWorks 7, including products where VxWorks is bundled by an OEM. The bundle lists no precise versions, CPEs, or Oracle product mapping.
Exploitation context
No active exploitation is established in the provided evidence. The CVE is not listed as KEV in the bundle, and the cited references do not provide exploit status, proof-of-concept details, or weaponization evidence.
Researcher notes
The public record is sparse: description-level allocator flaw, no CVSS, no CWE, no CPEs, and no named vulnerable builds. Avoid assuming remote code execution or broad Oracle impact without vendor confirmation. Focus validation on product composition and advisory correlation.
Mitigation direction
- Check Wind River security guidance for CVE-2020-35198 and applicable fixes.
- Ask OEMs whether shipped firmware includes affected VxWorks 7 components.
- Apply vendor or OEM updates when explicitly available.
- Limit unnecessary network reachability to embedded systems pending vendor guidance.
Validation and detection
- Inventory devices, firmware, and SBOMs for Wind River VxWorks 7.
- Match build versions against Wind River and OEM advisories.
- Review Oracle April 2022 CPU only for products you actually run.
- Document unresolved systems where vendor impact is unknown.
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-2020-35198 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://support2.windriver.com/index.php?page=security-noticesCVE reference · x_refsource_MISC
- https://support2.windriver.com/index.php?page=cve&on=view&id=CVE-2020-35198CVE reference · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpuapr2022.htmlCVE 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.