disable_functions bypass - dl function
Previousdisable_functions bypass - php-fpm/FastCGINextdisable_functions bypass - PHP 7.0-7.4 (*nix only)
Last updated
Last updated
Learn & practice AWS Hacking:
HackTricks Training AWS Red Team Expert (ARTE)
Learn & practice GCP Hacking: 
HackTricks Training GCP Red Team Expert (GRTE)
Important note:
dl is a PHP function that can be used to load PHP extensions. It the function isn't disabled it could be abused to bypass disable_functions and execute arbitrary commands.
However, it has some strict limitations:
The dl function must be present in the environment and not disabled
The PHP Extension must be compiled with the same major version (PHP API version) that the server is using (you can see this information in the output of phpinfo)
The PHP extension must be located in the directory that is defined by the extension_dir directive (you can see it in the output of phpinfo). It's very unprobeable that an attacker trying to abuse the server will have write access over this directory, so this requirement probably will prevent you to abuse this technique).
If you meet these requirements, continue reading the post https://antichat.com/threads/70763/ to learn how to bypass disable_functions. Here is a summary:
The dl function is used to load PHP extensions dynamically during script execution. PHP extensions, typically written in C/C++, enhance PHP's functionality. The attacker, upon noticing the dl function is not disabled, decides to create a custom PHP extension to execute system commands.
PHP Version Identification:
The attacker determines the PHP version using a script (<?php echo 'PHP Version is '.PHP_VERSION; ?>).
PHP Source Acquisition:
Downloads the PHP source from the official PHP website or the archive if the version is older.
Local PHP Setup:
Extracts and installs the specific PHP version on their system.
Extension Creation:
Studies creating PHP extensions and inspects the PHP source code.
Focuses on duplicating the functionality of the exec function located at ext/standard/exec.c.
ZEND_MODULE_API_NO:
The ZEND_MODULE_API_NO in bypass.c must match the current Zend Extension Build, retrievable with:
PHP_FUNCTION Modification:
For recent PHP versions (5, 7, 8), PHP_FUNCTION(bypass_exec) may need adjustment. The provided code snippet details this modification.
bypass.c:
Implements the core functionality of the custom extension.
php_bypass.h:
Header file, defining extension properties.
config.m4:
Used by phpize to configure the build environment for the custom extension.
Compilation Commands:
Uses phpize, ./configure, and make to compile the extension.
Resulting bypass.so is then located in the modules subdirectory.
Cleanup:
Runs make clean and phpize --clean after compilation.
Version Compatibility:
Ensures PHP API versions match between the attacker's and victim's systems.
Extension Loading:
Utilizes the dl function, circumventing restrictions by using relative paths or a script to automate the process.
Script Execution:
The attacker uploads bypass.so and a PHP script to the victim's server.
The script uses dl_local function to dynamically load bypass.so and then calls bypass_exec with a command passed via the cmd query parameter.
The attacker can now execute commands by accessing: http://www.example.com/script.php?cmd=<command>
This detailed walkthrough outlines the process of creating and deploying a PHP extension to execute system commands, exploiting the dl function, which should ideally be disabled to prevent such security breaches.
Learn & practice AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE)
Learn & practice GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE)
