CVE-2019-3730
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 Micro Edition Suite versions prior to 4.1.6.3 (in 4.1.x) and prior to 4.4 (in 4.2.x and 4.3.x), are vulnerable to an Information Exposure Through an Error Message vulnerability, also known as a “padding oracle attack vulnerability”. 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 Micro Edition Suite versions prior to 4.1.6.3 and 4.4 contain a padding oracle vulnerability. The vulnerability allows remote attackers to exploit error messages from decryption operations to deduce plaintext, effectively allowing decryption of sensitive data through repeated oracle queries.
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.1.0, < 4.1.6.3>= 4.2.0, < 4.4.0CVSS 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.
-
Identify installed RSA BSAFE Micro Edition Suite versionCheck the product version via the system inventory, software bill of materials, or the version information embedded in the BSAFE library files. Common locations include the product documentation, version metadata file, or runtime version string if exposed by the application.Affected if The installed version is 4.1.0 through 4.1.6.2 (inclusive), or 4.2.0 through 4.3.x (inclusive)
-
Confirm the product is RSA BSAFE Micro Edition SuiteVerify that the software component in use is specifically RSA BSAFE Micro Edition Suite (or Dell Bsafe Micro Edition Suite) and not another RSA BSAFE product line.Affected if The product is RSA BSAFE Micro Edition Suite or Dell Bsafe Micro Edition Suite within the affected version ranges
-
Determine if decryption operations are accessibleAudit the application or service configuration to identify whether decryption functionality using BSAFE is exposed through APIs, web services, or other interfaces that accept encrypted input from untrusted sources.Affected if Decryption operations using the vulnerable BSAFE component are accessible to remote or untrusted callers
-
Check for oracle-enabled error handlingReview application logs and error responses from decryption endpoints to determine whether detailed error messages (especially padding-related errors) are returned to clients. Test by sending deliberately malformed ciphertext and observing the response.Affected if Detailed decryption error messages (padding failures, oracle responses) are returned to callers, enabling repeated oracle queries
You are affected if RSA BSAFE Micro Edition Suite version is below 4.1.6.3 (for 4.1.x) or below 4.4.0 (for 4.2.x/4.3.x) AND decryption operations using this library are exposed to untrusted input with verbose error responses.
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.1.6.34.4.0
Upgrade RSA BSAFE Micro Edition Suite to version 4.1.6.3 or later (for 4.1.x) or version 4.4 or later (for 4.2.x/4.3.x).
- Consultation3.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3730 — 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-3730 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