CVE-2013-3242 : 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	–	–	6.77%	–	–
2022-04-03	–	–	6.77%	–	–
2022-10-09	–	–	6.22%	–	–
2022-11-13	–	–	6.22%	–	–
2022-11-20	–	–	6.22%	–	–
2022-12-25	–	–	6.22%	–	–
2023-01-01	–	–	6.22%	–	–
2023-01-15	–	–	5.81%	–	–
2023-03-12	–	–	–	3.26%	–
2023-10-01	–	–	–	3.32%	–
2023-11-19	–	–	–	3.04%	–
2024-02-11	–	–	–	3.04%	–
2024-06-02	–	–	–	3%	–
2024-07-28	–	–	–	2.2%	–
2024-09-29	–	–	–	2.11%	–
2024-11-17	–	–	–	2.11%	–
2024-12-08	–	–	–	2.05%	–
2024-12-22	–	–	–	1.76%	–
2025-02-02	–	–	–	1.58%	–
2025-01-19	–	–	–	1.76%	–
2025-02-02	–	–	–	1.58%	–
2025-03-18	–	–	–	–	0.21%
2025-03-30	–	–	–	–	0.18%
2025-04-15	–	–	–	–	0.18%
2025-04-15	–	–	–	–	0.18,%

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	79%
2022-04-03	91%
2022-10-09	9%
2022-11-13	91%
2022-11-20	9%
2022-12-25	91%
2023-01-01	9%
2023-01-15	9%
2023-03-12	9%
2023-10-01	9%
2023-11-19	9%
2024-02-11	91%
2024-06-02	91%
2024-07-28	9%
2024-09-29	89%
2024-11-17	9%
2024-12-08	89%
2024-12-22	88%
2025-02-02	87%
2025-01-19	88%
2025-02-02	87%
2025-03-18	41%
2025-03-30	36%
2025-04-15	4%
2025-04-15	4%

------------------------------------------------------------------ Joomla! <= 3.0.3 (remember.php) PHP Object Injection Vulnerability ------------------------------------------------------------------ [-] Software Link: http://www.joomla.org/ [-] Affected Versions: Version 3.0.3 and earlier 3.0.x versions. Version 2.5.9 and earlier 2.5.x versions. [-] Vulnerability Description: The vulnerable code is located in /plugins/system/remember/remember.php: 34. $hash = JApplication::getHash('JLOGIN_REMEMBER'); 35. 36. if ($str = JRequest::getString($hash, '', 'cookie', JREQUEST_ALLOWRAW | JREQUEST_NOTRIM)) 37. { 38. // Create the encryption key, apply extra hardening using the user agent string. 39. // Since we're decoding, no UA validity check is required. 40. $privateKey = JApplication::getHash(@$_SERVER['HTTP_USER_AGENT']); 41. 42. $key = new JCryptKey('simple', $privateKey, $privateKey); 43. $crypt = new JCrypt(new JCryptCipherSimple, $key); 44. $str = $crypt->decrypt($str); 45. $cookieData = @unserialize($str); User input passed through cookies is not properly sanitized before being used in an unserialize() call at line 45. This could be exploited to inject arbitrary PHP objects into the application scope. Successful exploitation of this vulnerability requires authentication because the attacker needs to know the "hash string" used to read the cookie parameter at line 36. [-] Solution: Upgrade to version 2.5.10, 3.0.4 or 3.1.0. [-] Disclosure Timeline: [04/12/2012] - Vendor alerted for a possible vulnerability [13/02/2013] - Vulnerability confirmed and proof of concept sent to the vendor [24/04/2013] - Vendor update released [26/04/2013] - Public disclosure [-] CVE Reference: The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-3242 to this vulnerability. [-] Credits: Vulnerability discovered by Egidio Romano. [-] Original Advisory: http://karmainsecurity.com/KIS-2013-04