|
|
| (7 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | =Able to run arbitrary executables on Windows Terminal server=
| |
| − | *<B>Type</B>: Local arbitrary code execution
| |
| − | *<B>Status</B>: <FONT color=red>Not fixed</FONT>
| |
| | | | |
| − | Microsoft Windows' bootloader by default checks the header of the executable it is given, to determine whether it is an EXE, BAT or COM file, and automatically runs it as the proper type. The current configuration on the Nikhef Windows Terminal Server blocks the loading of arbitrary EXE and COM files, but not arbitrary BAT files. Thus, by renaming the file extension from EXE to BAT, this security feature is circumvented, and the executable executed.
| |
| − |
| |
| − | =PHP scripts on webserver run under 'web' account=
| |
| − | *<B>Type</B>: Local privilege escalation
| |
| − | *<B>Status</B>: <FONT color=blue>Fixed</FONT>
| |
| − |
| |
| − | Any PHP script run on the webserver (by, for example, dropping the scriptfile into the user's public_html directory) executes under the 'web' account. This allows users to escalate their privilege (if the 'web' account has more rights than the user's account).
| |
| − |
| |
| − | =PHP on webserver able to reach main filesystem=
| |
| − | *<B>Type</B>:
| |
| − | *<B>Status</B>: <FONT color=red>Not fixed</FONT>
| |
| − |
| |
| − | The PHP installation running on the webserver is able to reach the main filesystem (at least the *nix side) without any problems. In fact, several directories are exposed to the web (by design). This allows PHP scripts to access the filesystem, and (if rights permit) even write to the filesystem.
| |
| − |
| |
| − | =PHP on webserver able to exec arbitrary executables=
| |
| − | *<B>Type</B>:
| |
| − | *<B>Status</B>: <FONT color=red>Not fixed</FONT>
| |
| − |
| |
| − | Using PHP's built-in 'exec' command, a PHP script can run arbitrary executables on the webserver.
| |