LiveActive security incident?Get immediate response
CVE Record

CVE-2019-3732: RSA BSAFE Crypto-C Micro Edition, versions prior to 4.0.5.3 (in 4.0.x) and versions prior to 4.1.3.3 (in 4....

RSA BSAFE Crypto-C Micro Edition, versions prior to 4.0.5.3 (in 4.0.x) and versions prior to 4.1.3.3 (in 4.1.x), and RSA Micro Edition Suite, versions prior to 4.0.11 (in 4.0.x) versions prior to 4.1.6.1 (in 4.1.x) and versions prior to 4.3.3 (4.2.x and 4.3.x) are vulnerable to an Information Exposure Through Timing Discrepancy. A malicious remote user could potentially exploit this vulnerability to extract information leaving data at risk of exposure.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw affects RSA BSAFE crypto libraries used inside applications and products. A remote attacker might infer sensitive information from timing differences, putting confidentiality at risk. It is not a direct system takeover issue, but crypto libraries can be embedded deep in products, so organizations should identify any use of the affected versions.

Executive priority

Treat this as a targeted confidentiality risk, not an emergency takeover scenario. Prioritize discovery in externally reachable, high-value, or regulated-data systems that rely on affected RSA BSAFE cryptographic components.

Technical view

CVE-2019-3732 is an Information Exposure Through Timing Discrepancy vulnerability in RSA BSAFE Crypto-C Micro Edition and RSA Micro Edition Suite. The CVSS 3.0 vector is network-accessible, unauthenticated, no user interaction, high confidentiality impact, but high attack complexity.

Likely exposure

Exposure is most likely in software, appliances, or embedded systems that include affected RSA BSAFE Crypto-C Micro Edition or RSA Micro Edition Suite versions. Direct internet exposure depends on how a product uses the vulnerable cryptographic library.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The attack is described as possible for a malicious remote user, but high attack complexity limits practical likelihood without favorable conditions.

Researcher notes

The public detail provided is sparse. Focus on component identification, version mapping, and vendor advisories. Avoid assuming exploitability in a product unless the affected BSAFE library is present and reachable through relevant cryptographic operations.

Mitigation direction

  • Inventory products and applications using RSA BSAFE Crypto-C Micro Edition or RSA Micro Edition Suite.
  • Upgrade Crypto-C Micro Edition 4.0.x to 4.0.5.3 or later.
  • Upgrade Crypto-C Micro Edition 4.1.x to 4.1.3.3 or later.
  • Upgrade Micro Edition Suite to the fixed versions named in Dell guidance.
  • Check Dell/RSA advisory guidance for product-specific remediation details.

Validation and detection

  • Confirm whether any internal or third-party products embed RSA BSAFE components.
  • Record exact BSAFE product and branch versions for each affected system.
  • Compare installed versions against the fixed thresholds in the CVE description.
  • Ask vendors whether their products include vulnerable BSAFE versions.
  • Track remediation evidence through vendor advisory references or updated component manifests.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-385: 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 lookup
cve · low confidence lookup

CVE-2019-3732 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.0MediumCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.9Medium
CVSS 3.0 vector shape for CVE-2019-3732Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
DellRSA BSAFE Crypto-C Micro EditionunspecifiedListed
DellRSA BSAFE MESunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-385 · source CWE mapping

Covert Timing Channel

Covert Timing Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.