Skip to content

Duplicate Advisory: motionEye vulnerable to RCE via unsanitized motion config parameter

High severity GitHub Reviewed Published Oct 3, 2025 to the GitHub Advisory Database • Updated Nov 3, 2025
Withdrawn This advisory was withdrawn on Nov 3, 2025

Package

pip motioneye (pip)

Affected versions

< 0.43.1b5

Patched versions

None

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-j945-qm58-4gjx. This link is maintained to preserve external references.

Original Description

MotionEye v0.43.1b4 and before is vulnerable to OS Command Injection in configuration parameters such as image_file_name. Unsanitized user input is written to Motion configuration files, allowing remote authenticated attackers with admin access to achieve code execution when Motion is restarted.

References

Published by the National Vulnerability Database Oct 3, 2025
Published to the GitHub Advisory Database Oct 3, 2025
Reviewed Nov 3, 2025
Withdrawn Nov 3, 2025
Last updated Nov 3, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

EPSS score

Weaknesses

Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-26f6-wm47-7h7j

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.