Bug #13426: ``status.php`` uses ``<name>`` component of ``/tmp/rules.packages.<name>`` filenames in shell command without encoding - pfSense - pfSense bugtracker

Actions

Copy link

Bug #13426

closed

``status.php`` uses ``<name>`` component of ``/tmp/rules.packages.<name>`` filenames in shell command without encoding

Added by Jim Pingle over 2 years ago. Updated almost 2 years ago.

Status:

Resolved

Priority:

High

Assignee:

Jim Pingle

Category:

Diagnostics

Target version:

2.7.0

Start date:

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

23.01

Release Notes:

Default

Affected Version:

Affected Architecture:

Description

If there is a file named /tmp/rules.packages.|<command>|.txt, then when an authenticated GUI user loads status.php, the GUI executes <command>.

In combination with another bug that lets users write arbitrary files, such as #13425, a user with sufficient privileges to access status.php could run a command directly or trick another administrator with privileges into running a command.

The commands which work here are of limited use as other characters which might make it more useful also make it fail to trigger. Furthermore, status.php is not linked in the GUI and is typically only run under direction of TAC, so opportunity for exploitation is fairly low.