CVE-2019-3732
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRSA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRSA BSAFE crypto library contains a timing side-channel vulnerability where cryptographic operations exhibit timing discrepancies that could allow a remote attacker to extract sensitive information such as plaintext or key material through statistical analysis of operation timing.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.0, < 4.0.5.3>= 4.0.0, < 4.0.11>= 4.1.0, < 4.1.6.1>= 4.2.0, < 4.3.3>= 4.1, < 4.1.3.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate RSA BSAFE crypto library filesSearch for BSAFE-related dynamic libraries (e.g., libbsafe, BSAFE*.dll, BSAFE*.so) or check product installation directories for Dell Bsafe or EMC RSA BSAFE componentsAffected if RSA BSAFE library files are present in the environment
-
Identify the specific RSA BSAFE productReview product documentation, installation metadata, or library version strings to determine whether the installation is Dell Bsafe Crypto C Micro Edition, Dell Bsafe Micro Edition Suite, or EMC RSA BSAFE Crypto CAffected if The identified product matches one of the three affected product lines
-
Determine the installed versionQuery the library version using system utilities (such as 'strings', version info in binary metadata, or product-specific version lookup commands) or check the product's version file or registry entryAffected if The version number can be obtained from the installation
-
Compare version against affected rangesMatch the installed version to the affected ranges: Dell Bsafe Crypto C Micro Edition: >=4.0 and <4.0.5.3; Dell Bsafe Micro Edition Suite: >=4.0.0 and <4.0.11, or >=4.1.0 and <4.1.6.1, or >=4.2.0 and <4.3.3; EMC RSA BSAFE Crypto C: >=4.1 and <4.1.3.3Affected if The installed version falls within any of the listed vulnerable version ranges
-
Verify active cryptographic usageReview application code or system configuration to confirm that the RSA BSAFE library is actively performing cryptographic operations (encryption, decryption, signing, key generation)Affected if The library is being called to execute cryptographic operations
The environment is affected if RSA BSAFE library files are present, the installed version falls within the vulnerable ranges, and cryptographic operations are being performed using the library.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data4.0.5.34.0.114.1.3.3
Update RSA BSAFE Crypto-C Micro Edition to version 4.0.5.3 or later (4.0.x) and 4.1.3.3 or later (4.1.x); update RSA Micro Edition Suite to 4.0.11+, 4.1.6.1+, or 4.3.3+ as applicable. Re-test all cryptographic operations after upgrade.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3732 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-3732 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data