CVE-2004-0079
No exploitation reported by the sources we read.
- Published2004-11-23
- WeaknessCWE-476
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The do_change_cipher_spec function in OpenSSL 0.9.6c to 0.9.6k, and 0.9.7a to 0.9.7c, allows remote attackers to cause a denial of service (crash) via a crafted SSL/TLS handshake that triggers a null dereference.
Timeline
dates in UTC- 2004-11-2305:00CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2004-0079?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2004-0079?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.0 | = 6.0 | no fix published | NVD |
| 6.0 | = 6.0\(1\) | no fix published | NVD |
| 6.0 | = 6.0\(2\) | no fix published | NVD |
| 6.0 | = 6.0\(3\) | no fix published | NVD |
| 6.0 | = 6.0\(4\) | no fix published | NVD |
| 6.0 | = 6.0\(4.101\) | no fix published | NVD |
| 6.1 | = 6.1 | no fix published | NVD |
| 6.1 | = 6.1\(1\) | no fix published | NVD |
| 6.1 | = 6.1\(2\) | no fix published | NVD |
| 6.1 | = 6.1\(3\) | no fix published | NVD |
| 6.1 | = 6.1\(4\) | no fix published | NVD |
| 6.1 | = 6.1\(5\) | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.0 | = 1.0.1 | no fix published | NVD |
| 1.0 | = 1.0.2 | no fix published | NVD |
| 1.0 | = 1.0.3 | no fix published | NVD |
| 1.1 | = 1.1 | no fix published | NVD |
| 1.1 | = 1.1.1 | no fix published | NVD |
| 1.2 | = 1.2.1 | no fix published | NVD |
| 1.2 | = 1.2.2 | no fix published | NVD |
| 1.2 | = 1.2_rc1 | no fix published | NVD |
| 1.2 | = 1.2_rc2 | no fix published | NVD |
| 1.3 | = 1.3 | no fix published | NVD |
| 1.3 | = 1.3.1 | no fix published | NVD |
| 1.3 | = 1.3_rc1 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.9 | = 0.9.6c | no fix published | NVD |
| 0.9 | = 0.9.6d | no fix published | NVD |
| 0.9 | = 0.9.6e | no fix published | NVD |
| 0.9 | = 0.9.6f | no fix published | NVD |
| 0.9 | = 0.9.6g | no fix published | NVD |
| 0.9 | = 0.9.6h | no fix published | NVD |
| 0.9 | = 0.9.6i | no fix published | NVD |
| 0.9 | = 0.9.6j | no fix published | NVD |
| 0.9 | = 0.9.6k | no fix published | NVD |
| 0.9 | = 0.9.7 | no fix published | NVD |
| 0.9 | = 0.9.7a | no fix published | NVD |
| 0.9 | = 0.9.7b | no fix published | NVD |
63 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- www.securityfocus.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2004-11-23
- Last Modified
- 2026-06-16
- NVD status
- Modified
Frequently asked questions
What is CVE-2004-0079?
Is CVE-2004-0079 actively exploited?
What is the CVSS score for CVE-2004-0079?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.