LiveActive security incident?Get immediate response
CVE Record

CVE-2019-3728: RSA BSAFE Crypto-C Micro Edition versions from 4.0.0.0 before 4.0.5.4 and from 4.1.0 before 4.1.4, RSA BSAF...

RSA BSAFE Crypto-C Micro Edition versions from 4.0.0.0 before 4.0.5.4 and from 4.1.0 before 4.1.4, RSA BSAFE Micro Edition Suite versions from 4.0.0 before 4.0.13 and from 4.1.0 before 4.4 and RSA Crypto-C versions from 6.0.0 through 6.4.* are vulnerable to an out-of-bounds read vulnerability when processing DSA signature. A malicious remote user could potentially exploit this vulnerability to cause a crash in the library of the affected system.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a denial-of-service risk in RSA BSAFE cryptographic libraries. A remote unauthenticated attacker could trigger a crash when an affected system processes a DSA signature. The business risk is service disruption in products or embedded systems that still include vulnerable BSAFE versions.

Executive priority

Treat as high priority where BSAFE is present in reachable services because exploitation can disrupt availability without authentication. It is lower priority for isolated systems or environments where affected DSA processing is not reachable.

Technical view

CVE-2019-3728 is a CWE-125 out-of-bounds read in DSA signature processing affecting specified RSA BSAFE Crypto-C Micro Edition, Micro Edition Suite, and RSA Crypto-C versions. The CVSS 3.1 vector is network, low complexity, no privileges, no user interaction, with high availability impact only.

Likely exposure

Exposure is most likely in legacy applications, appliances, or embedded products that bundle RSA BSAFE rather than systems visibly branded as RSA. Inventory must trace linked cryptographic libraries and vendor-supplied components.

Exploitation context

The provided sources support remote unauthenticated crash potential but do not show confirmed active exploitation. CISA KEV status is false in the bundle. No exploit details are needed to validate exposure.

Researcher notes

The evidence supports availability impact only: no confidentiality or integrity impact is described. Affected-version details are clear for several BSAFE branches, but remediation detail for RSA Crypto-C 6.0.0 through 6.4.* should be confirmed from Dell guidance.

Mitigation direction

  • Identify products and binaries that include RSA BSAFE libraries.
  • Upgrade BSAFE Crypto-C Micro Edition to fixed versions referenced by Dell.
  • Upgrade BSAFE Micro Edition Suite to fixed versions referenced by Dell.
  • For RSA Crypto-C 6.0.0 through 6.4.*, check Dell guidance for remediation.
  • Prioritize internet-facing or high-availability services first.

Validation and detection

  • Check software bills of materials for RSA BSAFE components.
  • Confirm deployed BSAFE version ranges against the CVE record.
  • Ask vendors whether their products bundle affected RSA BSAFE libraries.
  • Review crash telemetry around DSA signature handling in exposed services.
  • Document compensating controls where upgrade timing is vendor-dependent.
Prepared
Confidence
high
Sources
5

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-125: 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-3728 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

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
4Source 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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2019-3728Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
DellRSA BSAFE Crypto-C Micro Edition4.0.0.0, 4.1.0unaffected
DellRSA BSAFE Micro Edition Suite4.0.0, 4.1.0unaffected
DellRSA Crypto-C6.0.0affected
Weakness

CWE details

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

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.