Jordak Writeup - Proving Grounds
Created October 8, 2026 • Last updated October 8, 2026 • 2 min read
Jordak runs Jorani v1.0.0, a leave-management application vulnerable to CVE-2023-26469, an unauthenticated log-poisoning chain that leads to remote code execution. A public exploit script gives a shell as jordak, and a passwordless sudo rule for /usr/bin/env is a one-line root escape.
Reconnaissance
Nmap
Scan the target for open services.
PORT STATE SERVICE 22/tcp open ssh 80/tcp open http
Only SSH and HTTP. Enumerating the web root turns up a Jorani v1.0.0 installation at /jorani, confirmed by the application footer. Jorani <=1.0.0 is affected by CVE-2023-26469, a log-poisoning to LFI-to-RCE chain: application logs are poisoned with PHP code, then the app is triggered to include the poisoned log file.
Exploitation
Jorani log poisoning RCE (CVE-2023-26469)
Use the public exploit, which automates poisoning the log and triggering the include.
[+] Poisoning application log [+] Triggering log inclusion [+] Shell sent to listener
With a listener running, the exploit poisons the logs, triggers the include and a reverse shell connects back as jordak. Stabilize it.
jordak@jordak:~$
Privilege Escalation
sudo env (GTFOBins)
Check sudo privileges.
User jordak may run the following commands on jordak:
(ALL : ALL) ALL
(ALL) NOPASSWD: /usr/bin/env
A passwordless rule for /usr/bin/env is a well-known GTFOBins escape: env can execute an arbitrary command, so running it via sudo hands over a root shell immediately.
# id uid=0(root) gid=0(root) groups=0(root)
Related
References
-
Jorani <=1.0.0 unauthenticated log poisoning to remote code execution.
-
Abusing a passwordless sudo rule on env for privilege escalation.