CVE-2000-0685 : 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	–	–	–	2.81%	–
2023-10-29	–	–	–	2.81%	–
2024-02-11	–	–	–	3.93%	–
2024-06-02	–	–	–	3.93%	–
2024-12-22	–	–	–	3.71%	–
2025-01-19	–	–	–	3.71%	–
2025-03-18	–	–	–	–	4.21%
2025-03-30	–	–	–	–	5.2%
2025-03-30	–	–	–	–	5.2,%

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	89%
2023-10-29	9%
2024-02-11	92%
2024-06-02	92%
2024-12-22	92%
2025-01-19	92%
2025-03-18	88%
2025-03-30	89%
2025-03-30	89%

source: https://www.securityfocus.com/bid/1525/info In February of 2000 CERT Coordination Center released an advisory titled "Malicious HTML Tags Embedded in Client Web Requests" (advisory attached in 'Credit' section"). This advisory was a joint release by the CERT Coordination Center, DoD-CERT, the DoD Joint Task Force for Computer Network Defense (JTF-CND), the Federal Computer Incident Response Capability (FedCIRC), and the National Infrastructure Protection Center (NIPC). The point of the advisory in essence was a warning about client side vulnerabilities brought about by malicious scripting from Rogue websites which could be exploited to run code on client side browsers (acting as unwary interpreters for the scripting in question). A number of webserver have suffered from this problem including 'Weblogic' from BEA Systems. In this particular case if a user can upload text in the form of JSP or JHTML code to the webserver (possibly via a web form etc.) a malicious end user might execute this code. " Assume that there is an application on the WebLogic server that writes user entered data to a file called "temp.txt". Given below is JHTML/JSP code that will print "Hello World": <java>out.println("Hello World");</java> (JHTML) -or- <% out.println("Hello World"); %> (JSP) If this code is somehow inserted in the file "temp.txt" via an application, then the following can be used to invoke forced compilation and execution of "temp.txt": http://weblogic.site/*.jhtml/path/to/temp.txt (JHTML) -or- http://weblogic.site/*.jsp/path/to/temp.txt "