Prabhatverma47

**Name of the Vulnerable Software and Affected Versions** MotionEye versions 0.43.1b4 and earlier **Description** MotionEye is susceptible to a command injection issue that allows attackers to achieve Remote Code Execution (RCE). The vulnerability arises because MotionEye writes user-supplied values directly into Motion configuration files without proper sanitization. Specifically, values provided in configuration fields exposed through the Web UI, such as `image file name` and `movie filename`, are written to `/etc/motioneye/camera-*.conf`. When the Motion service restarts, the Motion binary parses these configuration files, interpreting injected characters as shell commands. This allows attackers to execute arbitrary code, potentially gaining full control of the MotionEye container and, depending on container privileges, the host environment. The vulnerability is exploitable by remote authenticated attackers with admin access. Client-side validation can be bypassed by overriding the validation function in the browser console. A proof of concept demonstrates the ability to create files with root permissions and establish a reverse shell connection. **Recommendations** Versions prior to 0.43.1b4 are affected. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: OctoPrint versions prior to 1.11.3 Description: OctoPrint is a web interface for controlling consumer 3D printers. Versions up to and including 1.11.2 are susceptible to a flaw that permits an authenticated attacker to upload a file with a specially crafted filename. This can lead to arbitrary command execution if the filename is included in a command defined within a system event handler and that event is triggered. If no event handlers executing system commands with uploaded filenames as parameters have been configured, this issue has no impact. Recommendations: OctoPrint versions prior to 1.11.3: Disable event handlers that include filename-based placeholders by setting their `enabled` property to `False` or unchecking the "Enabled" checkbox in the GUI based Event Manager. OctoPrint versions prior to 1.11.3: Set `feature.enforceReallyUniversalFilenames` to `true` in `config.yaml` and restart OctoPrint, then vet existing uploads and delete any suspicious files. OctoPrint versions prior to 1.11.3: Avoid exposing OctoPrint on hostile networks and restrict access to authorized users.