Lessons Learned
LFI allows us to enumerate files and call and execute malicious code on the server
Sensitive information was disclosed, why did we have the pwdbackup.txt file on deck?
Log file poisoning. Since the log file was storing the user agent (user controlled data) without any input validation, we were able to inject malicious code into the server that we executed using the LFI vulnerability
Security misconfiguration that lead to a race condition in phpinfo.php file. This required two conditions to be present: (1) an LFI vulnerability which we already discussed, and (2) a script that displays the output of the phpinfo() configuration. The administrators should have disabled the phpinfo() function in all production environments.
The password was reused with the VNC file.
Last updated
Was this helpful?