dbcve.org
Firewall Services ModuleHardware / appliance · Cisco

CVE-2004-0112

MEDIUM · 5.0 CVSS v2.0 Published 2004-11-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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 SSL/TLS handshaking code in OpenSSL 0.9.7a, 0.9.7b, and 0.9.7c, when using Kerberos ciphersuites, does not properly check the length of Kerberos tickets during a handshake, which allows remote attackers to cause a denial of service (crash) via a crafted SSL/TLS handshake that causes an out-of-bounds read.

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.7a through 0.9.7c contain a flaw in SSL/TLS handshaking code when Kerberos ciphersuites are used. The code fails to properly validate the length of Kerberos tickets during the handshake, allowing a remote attacker to send a crafted SSL/TLS handshake with a malformed Kerberos ticket that triggers an out-of-bounds read and causes a denial of service (crash).

MitigationUpgrade to OpenSSL 0.9.7d or later which contains the fix for proper Kerberos ticket length validation. As a workaround, disable Kerberos ciphersuites if they are not required.

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
Firewall Services ModuleHardware / appliance
Affected:all versions= 1.1.2= 1.1.3= 1.1_\(3.005\)= 2.1_\(0.208\)
Ciscoworks Common Management FoundationApplication
Affected:= 2.1
Ciscoworks Common ServicesApplication
Affected:= 2.2
FreeBSDOperating system
Affected:= 4.8= 4.9= 5.1= 5.2= 5.2.1
Enterprise LinuxOperating system
Affected:= 3.0
Enterprise Linux DesktopOperating system
Affected:= 3.0
LinuxOperating system
Affected:= 7.2= 7.3= 8.0
iOSOperating system
Affected:= 12.1\(11\)e= 12.1\(11b\)e= 12.1\(11b\)e12= 12.1\(11b\)e14= 12.1\(13\)e9= 12.1\(19\)e1= 12.2\(14\)sy= 12.2\(14\)sy1= 12.2sy= 12.2za

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
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 checks

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

  1. Identify the OpenSSL version installed
    Run 'openssl version' or check the OpenSSL package version installed via the system package manager
    Affected if The version is 0.9.7a, 0.9.7b, or 0.9.7c (the vulnerable versions before 0.9.7d)
  2. Confirm Kerberos ciphersuite support in OpenSSL
    Run 'openssl ciphers -v | grep -i kerberos' or inspect the OpenSSL build configuration for Kerberos support
    Affected if OpenSSL was built with Kerberos (GSSAPI/KRB5) cipher support enabled
  3. Check if Kerberos ciphersuites are in the enabled cipher list
    Review SSL/TLS configuration files or application settings to see if KRB5-based ciphers are listed in the enabled ciphersuites
    Affected if Kerberos ciphersuites (such as KRB5-MD5, KRB5-DES-CBC3-MD5, etc.) are enabled in the SSL/TLS configuration
  4. Verify if the system accepts SSL/TLS connections using Kerberos ciphers
    Attempt an SSL/TLS handshake with a Kerberos ciphersuite or review SSL/TLS server logs for cipher negotiation
    Affected if The server or client negotiates a Kerberos ciphersuite during an SSL/TLS handshake

The environment is affected if OpenSSL version 0.9.7a-0.9.7c is installed AND Kerberos ciphersuites are enabled and actually used in SSL/TLS connections

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 to OpenSSL 0.9.7d or later which contains the fix for proper Kerberos ticket length validation. As a workaround, disable Kerberos ciphersuites if they are not required.

Fix this in Firewall Services Module Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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