OpenSSLFramework / library
CVE-2002-0659
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 ASN1 library in OpenSSL 0.9.6d and earlier, and 0.9.7-beta2 and earlier, allows remote attackers to cause a denial of service via invalid encodings.
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 confidenceThe ASN.1 library in OpenSSL versions 0.9.6d and earlier, and 0.9.7-beta2 and earlier, contains a parsing vulnerability that allows remote attackers to cause a denial of service by sending specially crafted invalid ASN.1 encodings.
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
OpenSSLFramework / library
= 0.9.1c= 0.9.2b= 0.9.3= 0.9.4= 0.9.5= 0.9.5a= 0.9.6= 0.9.6a= 0.9.6b= 0.9.6c= 0.9.6d= 0.9.7
HTTP ServerWeb server / proxy
= 9.0.1= 9.2.0all versions= 1.0.2= 1.0.2.1s= 1.0.2.2= 3.1= 3.1.1= 3.1.2= 3.3= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4= 10.1= 10.1.1= 10.1.2= 10.1.3= 10.1.4= 10.1.5CVSS 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.
-
Check installed OpenSSL versionRun 'openssl version -a' on the command line to display the full OpenSSL version information including build options and platformAffected if The version displayed is 0.9.6d or earlier, or 0.9.7 beta2 or earlier (versions 0.9.1c through 0.9.6d, or 0.9.7 through 0.9.7-beta2)
-
Check Oracle HTTP Server versionLocate the Oracle HTTP Server installation and check the version file or run 'httpd -v' from the ORACLE_HOME/Apache/Apache/bin directoryAffected if The version is 9.0.1 or 9.2.0
-
Check Oracle Application Server versionLocate the Oracle Application Server installation and check the version using the Oracle inventory or run 'iasversion' from the ORACLE_HOME/bin directoryAffected if The version is 1.0.2, 1.0.2.1s, 1.0.2.2, or any version listed as 'all versions' in the affected list
-
Check Oracle Corporate Time Outlook Connector versionCheck the installed version through Windows Add/Remove Programs or examine the program's properties in the installation directoryAffected if The version is 3.1, 3.1.1, 3.1.2, or 3.3
-
Check Apple Mac OS X versionRun 'sw_vers' from the command line or check 'About This Mac' from the Apple menuAffected if The version is 10.0, 10.0.1, 10.0.2, 10.0.3, 10.0.4, 10.1, 10.1.1, 10.1.2, 10.1.3, 10.1.4, or 10.1.5
The environment is affected if OpenSSL versions 0.9.6d or earlier (or 0.9.7-beta2 or earlier) are installed, or if any Oracle or Apple product listed with the specific affected versions is running.
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 dataUpgrade to a patched version of OpenSSL (0.9.6e or later, or 0.9.7-beta3 or later). If immediate patching is not possible, consider network-level filtering of malformed ASN.1 data or disabling affected SSL/TLS services until the upgrade can be completed.
Fix this in OpenSSL
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0659 — 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-2002-0659 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