dbcve.org
OpenSSLFramework / library

CVE-2002-0655

HIGH · 7.5 CVSS v2.0 Published 2002-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
OpenSSL 0.9.6d and earlier, and 0.9.7-beta2 and earlier, does not properly handle ASCII representations of integers on 64 bit platforms, which could allow attackers to cause a denial of service and possibly execute arbitrary code.

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 confidence

OpenSSL versions 0.9.6d and earlier, and 0.9.7-beta2 and earlier, contain a flaw in how they handle ASCII representations of integers on 64-bit platforms. This improper handling can lead to denial of service conditions and potentially allow attackers to execute arbitrary code due to memory corruption or improper integer parsing.

MitigationUpgrade OpenSSL to a version newer than 0.9.6d or 0.9.7-beta2 (patches were released in 2002 for this issue). On 64-bit platforms, verify all OpenSSL installations are patched and test application compatibility after the upgrade.

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
Affected:= 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
Affected:= 9.0.1= 9.2.0
Application ServerApplication
Affected:all versions= 1.0.2= 1.0.2.1s= 1.0.2.2
Corporate Time Outlook ConnectorApplication
Affected:= 3.1= 3.1.1= 3.1.2= 3.3
Mac Os XOperating system
Affected:= 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.5

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

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

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

  1. Identify OpenSSL version
    Run 'openssl version' or 'openssl version -a' to display the installed OpenSSL version number
    Affected if Version is 0.9.6d or earlier, or 0.9.7-beta2 or earlier (including 0.9.1c through 0.9.6d, and 0.9.7 through 0.9.7-beta2)
  2. Determine system architecture
    Run 'uname -m' or check system information to confirm the platform is 64-bit (x86_64, amd64, ia64)
    Affected if System is a 64-bit platform and OpenSSL version is in the affected range above
  3. Check for Oracle HTTP Server installation
    Locate Oracle HTTP Server installation and check the bundled OpenSSL version (typically in the Apache directory)
    Affected if Oracle HTTP Server versions 9.0.1 or 9.2.0 are installed with bundled vulnerable OpenSSL
  4. Check for Oracle Application Server installation
    Identify Oracle Application Server installation and verify its OpenSSL component version
    Affected if Oracle Application Server is installed (any version listed: all versions, 1.0.2, 1.0.2.1s, 1.0.2.2) with vulnerable OpenSSL
  5. Check for Apple Mac OS X version
    Run 'sw_vers' or check System Profiler to identify the macOS version
    Affected if Mac OS X version is 10.0 through 10.1.5 (any of the listed versions)

Environment is affected if OpenSSL version 0.9.6d or earlier (or 0.9.7-beta2 or earlier) is installed on a 64-bit platform, or if any listed Oracle/Apple product version with bundled vulnerable OpenSSL is present.

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

Upgrade OpenSSL to a version newer than 0.9.6d or 0.9.7-beta2 (patches were released in 2002 for this issue). On 64-bit platforms, verify all OpenSSL installations are patched and test application compatibility after the upgrade.

Fix this in OpenSSL Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-0655 — 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-2002-0655 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