CVE-2001-1130 : 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	–	–	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,%

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	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.