CVE-2006-3894
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 · uneditedThe RSA Crypto-C before 6.3.1 and Cert-C before 2.8 libraries, as used by RSA BSAFE, multiple Cisco products, and other products, allows remote attackers to cause a denial of service via malformed ASN.1 objects.
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 confidenceThe RSA Crypto-C library before 6.3.1 and Cert-C library before 2.8 contain a vulnerability where malformed ASN.1 objects can trigger a denial of service. The vulnerability exists in the ASN.1 parsing logic and can be exploited remotely by sending specially crafted ASN.1 encoded data to affected systems.
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<= 2.7<= 6.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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 Dell Bsafe libraries on the systemSearch for files named libbsafecert, libbsafecrypto, or similar Bsafe library files using: find / -name '*bsafe*' -o -name '*certc*' 2>/dev/nullAffected if Dell Bsafe Cert-C or Crypto-C libraries are found on the system
-
Identify the installed version of Bsafe Cert-C libraryCheck the library file version using: strings <path_to_lib> | grep -i version or check any version metadata files in the library directory. Compare against affected versions <= 2.7Affected if The Cert-C library version is 2.7 or earlier
-
Identify the installed version of Bsafe Crypto-C libraryCheck the library file version using: strings <path_to_lib> | grep -i version or check any version metadata files. Compare against affected versions <= 6.3Affected if The Crypto-C library version is 6.3 or earlier
-
Verify if ASN.1 parsing functionality is in useReview application configurations and code that utilize the Bsafe libraries to determine if ASN.1 decoding/encoding functions are being called. Check application logs and dependencies for ASN.1 usage.Affected if ASN.1 parsing features of the Bsafe libraries are actively used by any application on the system
-
Check for running services that depend on Bsafe librariesIdentify processes or services that link to Bsafe libraries using: lsof +c 0 2>/dev/null | grep -i bsafe or review application dependency listsAffected if Any running service or application links to and uses the vulnerable Bsafe libraries
The environment is affected if Dell Bsafe Cert-C version 2.7 or earlier or Crypto-C version 6.3 or earlier is installed AND the ASN.1 parsing functionality is being used by any application on the system.
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 dataUpdate RSA Crypto-C to version 6.3.1 or later and Cert-C to version 2.8 or later. For Cisco products and other vendors using these libraries, apply vendor-specific patches when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-3894 — 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-2006-3894 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