Security readout for executives and security teams
Plain-English summary
This vulnerability is a timing side-channel issue in Dell BSAFE cryptographic libraries. In affected versions, an attacker with local access may be able to infer sensitive information by observing timing differences. The public bundle does not indicate active exploitation.
Executive priority
Treat this as a targeted confidentiality risk, not an internet-scale emergency. Prioritize regulated, multi-user, or appliance environments where affected BSAFE components process sensitive cryptographic material and local access is plausible.
Technical view
CVE-2020-35165 is a CWE-208 Observable Timing Discrepancy vulnerability affecting Dell BSAFE Crypto-C Micro Edition before 4.1.5 and Dell BSAFE Micro Edition Suite before 4.6. CVSS 3.1 is 5.1, with local attack vector, high complexity, no privileges, and high confidentiality impact.
Likely exposure
Exposure is most likely in software, appliances, firmware, or embedded systems that directly include the affected Dell BSAFE libraries. The bundle provides product and version boundaries but no CPEs, deployment prevalence, or downstream vendor list.
Exploitation context
The CVSS vector requires local access and high attack complexity. No CISA KEV listing or cited source in the bundle supports active exploitation. The main concern is confidentiality loss through timing observations, not integrity or availability impact.
Researcher notes
The source bundle does not name the specific cryptographic operation, affected API, proof of concept, or patch mechanics. Validation should focus on accurate component/version discovery and vendor advisory alignment, especially for embedded or bundled dependencies where BSAFE may not be visible in normal asset inventories.
Mitigation direction
- Review Dell advisory DSA-2020-286 for official remediation guidance.
- Upgrade Crypto-C Micro Edition to 4.1.5 or later where applicable.
- Upgrade Micro Edition Suite to 4.6 or later where applicable.
- Ask product vendors for confirmation if BSAFE is embedded indirectly.
- Prioritize systems where local users can access cryptographic operations.
Validation and detection
- Inventory applications, firmware, and third-party products for Dell BSAFE usage.
- Confirm exact BSAFE library versions against the affected version boundaries.
- Check SBOMs or vendor attestations for embedded BSAFE components.
- Verify remediation using vendor-supported version reporting or package metadata.
- Document systems where version evidence is unavailable.
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.
CWE-208: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-35165 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
- Medium
- CVSS
- 5.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N1.43.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.1MediumVector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
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.
Observable Timing Discrepancy
Observable Timing Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.