Mysql 5.0.12 Exploit (Chrome)

CREATE FUNCTION sys_exec RETURNS INT SONAME 'exploit.so'; CREATE FUNCTION sys_eval RETURNS STRING SONAME 'exploit.so'; Suddenly, the attacker can run operating system commands:

Why /usr/lib/mysql/plugin/ ? This is the default UDF directory. If writable, the attack is trivial. If not, the attacker looks for world-writable directories like /tmp or /var/tmp and hopes the MySQL daemon’s library path includes them (rare, but possible in misconfigurations). With the .so file on disk, the attacker loads the UDF: mysql 5.0.12 exploit

SELECT @@secure_file_priv; Prior to MySQL 5.5, secure_file_priv was often empty, allowing file writes anywhere the mysql user had access. The attacker cannot upload binary files via standard SQL INSERT easily, but they can use INTO DUMPFILE . Exploit code (e.g., raptor_udf2.c or lib_mysqludf_sys.so ) is hex-encoded and written to disk. CREATE FUNCTION sys_exec RETURNS INT SONAME 'exploit