CVE-2007-3304

MEDIUMCVSS v2 · 4.74.7—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.7 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:L/AC:M/Au:N/C:N/I:N/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 3.3% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 3.3%CVSS v2: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Apache httpd 1.3.37, 2.0.59, and 2.2.4 with the Prefork MPM module, allows local users to cause a denial of service by modifying the worker_score and process_score arrays to reference an arbitrary process ID, which is sent a SIGUSR1 signal from the master process, aka "SIGUSR1 killer."

CVSS v2.0 (legacy)
4.7MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
4.7MEDIUMlow confidence
EG Risk
27
EG Risk 27/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation3% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
3.3%
EPSS %ILE
88th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 20, 2007

Last Modified

April 23, 2026

References (184)

Vendor Advisories for CVE-2007-3304(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuapache2-mpm-prefork (2.2.3-3.2ubuntu0.1) @ feisty2026-05-31ubuntu
redhatxml-commons-0:1.3.02-2jpp_1rh2010-08-04redhat
redhatrhn-modperl-0:1.29-16.rhel42008-06-30redhat
redhattomcat5-0:5.0.30-0jpp_10rh2008-06-30redhat
redhathttpd-0:2.0.59-1.el4s1.72007-07-13redhat
redhathttpd-0:2.0.52-32.3.ent2007-07-13redhat
redhathttpd-0:2.2.3-7.el52007-06-26redhat
redhatapache-0:1.3.27-12.ent2007-06-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.2.4-2: fixed in 2.2.4-2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.2.4-2: fixed in 2.2.4-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.2.4-2: fixed in 2.2.4-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.2.4-2: fixed in 2.2.4-2
—

Additional Vendor Advisories

(9)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 129 total refreshes for this CVE.

  1. 2026-10-09 20:00 UTCEPSS rescore
  2. 2026-10-08 16:33 UTCEPSS rescore
  3. 2026-10-07 23:37 UTCEPSS rescore
  4. 2026-10-06 15:09 UTCEPSS rescore
  5. 2026-10-05 17:37 UTCEPSS rescore
  6. 2026-10-04 13:48 UTCOSV refresh
  7. 2026-10-03 14:20 UTCEPSS rescore
  8. 2026-10-01 19:42 UTCEPSS rescore
  9. 2026-09-30 14:57 UTCEPSS rescore
  10. 2026-09-29 07:42 UTCEG score recompute
  11. 2026-09-18 19:20 UTCEPSS rescore
  12. 2026-09-17 19:20 UTCEPSS rescore
  13. 2026-09-15 03:04 UTCEPSS rescore
  14. 2026-09-15 03:03 UTCOSV refresh
  15. 2026-09-12 14:54 UTCEPSS rescore
  16. 2026-09-05 15:22 UTCEPSS rescore
  17. 2026-09-04 13:55 UTCEPSS rescore
  18. 2026-09-04 04:59 UTCEPSS rescore
  19. 2026-08-30 01:14 UTCEPSS rescore
  20. 2026-08-27 03:00 UTCOSV refresh
  21. 2026-08-10 16:08 UTCOSV refresh
  22. 2026-08-08 16:30 UTCEPSS rescore
  23. 2026-08-07 16:20 UTCEPSS rescore
  24. 2026-08-06 13:41 UTCEPSS rescore
  25. 2026-08-05 19:11 UTCEPSS rescore
Show 75 more
  1. 2026-08-04 15:03 UTCEPSS rescore
  2. 2026-08-03 10:28 UTCEPSS rescore
  3. 2026-07-30 16:22 UTCEPSS rescore
  4. 2026-07-30 01:25 UTCEPSS rescore
  5. 2026-07-28 15:30 UTCEPSS rescore
  6. 2026-07-26 13:32 UTCEG score recompute▲ 4.70
  7. 2026-07-25 17:00 UTCOSV refresh
  8. 2026-07-25 14:12 UTCEPSS rescore
  9. 2026-07-24 14:11 UTCEPSS rescore
  10. 2026-07-23 14:13 UTCEPSS rescore
  11. 2026-07-23 00:53 UTCEG score recompute
  12. 2026-07-23 00:32 UTCEG score recompute
  13. 2026-07-22 23:58 UTCEG score recompute
  14. 2026-07-22 21:37 UTCEG score recompute
  15. 2026-07-22 14:03 UTCEPSS rescore
  16. 2026-07-21 15:19 UTCEPSS rescore
  17. 2026-07-20 17:03 UTCEPSS rescore
  18. 2026-07-18 09:59 UTCEPSS rescore
  19. 2026-07-16 16:58 UTCEPSS rescore
  20. 2026-07-15 16:54 UTCEPSS rescore
  21. 2026-07-15 16:54 UTCEPSS rescore
  22. 2026-07-15 01:55 UTCEPSS rescore
  23. 2026-07-11 08:22 UTCEPSS rescore
  24. 2026-07-08 15:09 UTCEPSS rescore
  25. 2026-07-08 11:35 UTCOSV refresh
  26. 2026-07-06 16:22 UTCEPSS rescore
  27. 2026-07-06 02:19 UTCEPSS rescore
  28. 2026-07-05 02:26 UTCEPSS rescore
  29. 2026-07-04 06:27 UTCEPSS rescore
  30. 2026-07-04 06:27 UTCEPSS rescore
  31. 2026-07-02 14:00 UTCEPSS rescore
  32. 2026-07-01 15:02 UTCEPSS rescore
  33. 2026-07-01 15:02 UTCEPSS rescore
  34. 2026-06-30 23:19 UTCEPSS rescore
  35. 2026-06-30 23:19 UTCEPSS rescore
  36. 2026-06-29 14:02 UTCEPSS rescore
  37. 2026-06-29 14:02 UTCEPSS rescore
  38. 2026-06-28 14:03 UTCEPSS rescore
  39. 2026-06-28 04:52 UTCEPSS rescore
  40. 2026-06-27 03:04 UTCEPSS rescore
  41. 2026-06-25 13:46 UTCEPSS rescore
  42. 2026-06-25 13:46 UTCEPSS rescore
  43. 2026-06-24 14:02 UTCEPSS rescore
  44. 2026-06-24 14:02 UTCEPSS rescore
  45. 2026-06-23 21:29 UTCEPSS rescore
  46. 2026-06-23 21:29 UTCEPSS rescore
  47. 2026-06-21 14:53 UTCEPSS rescore
  48. 2026-06-21 01:56 UTCEPSS rescore
  49. 2026-06-21 01:56 UTCEPSS rescore
  50. 2026-06-19 23:36 UTCOSV refresh
  51. 2026-06-19 19:22 UTCEPSS rescore
  52. 2026-06-19 19:22 UTCEPSS rescore
  53. 2026-06-18 17:49 UTCEPSS rescore
  54. 2026-06-18 17:49 UTCEPSS rescore
  55. 2026-06-17 17:49 UTCEPSS rescore
  56. 2026-06-17 17:49 UTCEPSS rescore
  57. 2026-06-16 17:49 UTCEPSS rescore
  58. 2026-06-16 17:49 UTCEPSS rescore
  59. 2026-06-16 17:49 UTCEPSS rescore
  60. 2026-06-15 17:44 UTCEPSS rescore
  61. 2026-06-13 22:57 UTCEPSS rescore
  62. 2026-06-12 23:08 UTCEPSS rescore
  63. 2026-06-10 22:14 UTCEPSS rescore
  64. 2026-06-10 13:17 UTCEPSS rescore
  65. 2026-06-08 14:13 UTCEPSS rescore
  66. 2026-06-07 15:21 UTCEPSS rescore
  67. 2026-06-06 13:44 UTCEPSS rescore
  68. 2026-06-06 13:44 UTCEPSS rescore
  69. 2026-06-05 22:44 UTCEPSS rescore
  70. 2026-06-05 22:44 UTCEPSS rescore
  71. 2026-06-05 06:07 UTCEPSS rescore
  72. 2026-06-04 13:09 UTCEPSS rescore
  73. 2026-06-04 13:09 UTCEPSS rescore
  74. 2026-06-04 13:09 UTCEPSS rescore
  75. 2026-06-02 20:10 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-2007-3304?
CVE-2007-3304 is a medium vulnerability published on June 20, 2007. Apache httpd 1.3.37, 2.0.59, and 2.2.4 with the Prefork MPM module, allows local users to cause a denial of service by modifying the workerscore and processscore arrays to reference an arbitrary process ID, which is sent a SIGUSR1 signal from the master process, aka "SIGUSR1 killer."
When was CVE-2007-3304 disclosed?
CVE-2007-3304 was first published on June 20, 2007, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2007-3304 actively exploited?
CVE-2007-3304 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.3% probability of exploitation in the next 30 days (88th percentile of EPSS-scored CVEs).
How do I remediate CVE-2007-3304?
A fix for CVE-2007-3304 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2007-3304 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2007-3304

Explore →

Is Your Infrastructure Affected by CVE-2007-3304?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs