CVE-2001-1130 : 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	–	–	4.19%	–	–
2022-04-03	–	–	4.19%	–	–
2022-07-17	–	–	4.19%	–	–
2023-03-12	–	–	–	3.5%	–
2023-04-23	–	–	–	4.3%	–
2023-11-05	–	–	–	4.69%	–
2024-04-14	–	–	–	4.69%	–
2024-06-02	–	–	–	4.69%	–
2024-12-08	–	–	–	5.52%	–
2024-12-15	–	–	–	5.52%	–
2024-12-22	–	–	–	8.64%	–
2025-01-12	–	–	–	8.64%	–
2025-01-19	–	–	–	8.64%	–
2025-03-18	–	–	–	–	5.86%
2025-03-30	–	–	–	–	4.4%
2025-03-30	–	–	–	–	4.4,%

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	7%
2022-04-03	86%
2022-07-17	87%
2023-03-12	9%
2023-04-23	91%
2023-11-05	92%
2024-04-14	93%
2024-06-02	93%
2024-12-08	93%
2024-12-15	94%
2024-12-22	94%
2025-01-12	95%
2025-01-19	95%
2025-03-18	9%
2025-03-30	88%
2025-03-30	88%

source: https://www.securityfocus.com/bid/3208/info An input validation error exists in sdb, the SuSE Support Data Base. The problem exists in the sdbsearch.cgi script, which uses data directly from the 'Referer' header field from a HTTP request as a path when opening it's "keylist.txt" file. The keylist file contains a list of keywords and associated files, which are opened using Perl's open() command. If an attacker is able to create a malicious "keylist.txt" file on a vulnerable host, it may be possible for the attacker to cause arbitrary commands to be executed by the sdbsearch.cgi script. Proof of concept is very simple, just create harmful keylist.txt for instance in /tmp directory and send request to http server like this: GET /cgi-bin/sdbsearch.cgi?stichwort=keyword HTTP/1.0 Referer: http://szachy.org/../../../../../tmp (very deep traversal because we don't know what is DOCUMENT_ROOT) and an example content of our /tmp/keylist.txt create like this: $ echo -e "keyword\0touch exploitable|" > /tmp/keylist.txt After successful attempt there will be "exploitable" file in /tmp directory.