dbcve.org
Rsa Bsafe ToolkitsApplication · Emc

CVE-2013-6078

MEDIUM · 5.8 CVSS v2.0 Published 2014-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The default configuration of EMC RSA BSAFE Toolkits and RSA Data Protection Manager (DPM) 20130918 uses the Dual Elliptic Curve Deterministic Random Bit Generation (Dual_EC_DRBG) algorithm, which makes it easier for context-dependent attackers to defeat cryptographic protection mechanisms by leveraging unspecified "security concerns," aka the ESA-2013-068 issue. NOTE: this issue has been SPLIT from CVE-2007-6755 because the vendor announcement did not state a specific technical rationale for a change in the algorithm; thus, CVE cannot reach a conclusion that a CVE-2007-6755 concern was the reason, or one of the reasons, for this change.

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 · moderate confidence

The default configuration of EMC RSA BSAFE Toolkits and RSA Data Protection Manager (DPM) uses the Dual Elliptic Curve Deterministic Random Bit Generation (Dual_EC_DRBG) algorithm, which contains known cryptographic weaknesses that could allow attackers to predict random numbers and compromise cryptographic protections.

MitigationDisable Dual_EC_DRBG in the configuration and switch to a cryptographically secure alternative DRBG such as AES-CTR DRBG or HMAC DRBG, following vendor guidance for the affected products.

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
Rsa Bsafe ToolkitsApplication
Affected:all versions
Rsa Data Protection ManagerApplication
Affected:= 20130918

CVSS 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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:M/Au:N/C:P/I:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed RSA BSAFE Toolkit version
    Use system package manager or check product documentation for installed toolkit version. Common commands: 'rpm -q rsa-unsafe-libs' on Linux or check registry on Windows via regedit for RSA BSAFE components.
    Affected if Any version of RSA BSAFE Toolkit is installed (all versions are affected)
  2. Identify installed RSA Data Protection Manager version
    Check DPM application version through its management console, About section, or installed program version information.
    Affected if Version 20130918 is installed exactly
  3. Check Dual_EC_DRBG configuration status
    Locate the RSA BSAFE or DPM configuration file where cryptographic algorithm preferences are defined. Look for settings related to DRBG (Deterministic Random Bit Generation) or random number generator configuration. Search for 'Dual_EC' or 'DualEllipticCurve' in configuration files.
    Affected if Dual_EC_DRBG or DualEllipticCurve is listed as enabled or set as default in the configuration
  4. Verify the active DRBG algorithm in use
    Examine application logs, cryptographic configuration, or runtime settings to determine which DRBG algorithm is currently active. Check for 'Dual EC' or 'NIST SP 800-90' references in cryptographic provider settings.
    Affected if Dual_EC_DRBG is the actively used or default DRBG algorithm

You are affected if you have any version of RSA BSAFE Toolkit or RSA DPM version 20130918 with Dual_EC_DRBG enabled or set as the default random number generator in your configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable Dual_EC_DRBG in the configuration and switch to a cryptographically secure alternative DRBG such as AES-CTR DRBG or HMAC DRBG, following vendor guidance for the affected products.

Fix this in Rsa Bsafe Toolkits Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,260
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,216.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-6078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-6078 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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