Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Low severity, with a CVSS score of 3.1, published 3 October 2025.
- Which products and versions are affected?
- motioneye (PyPI) ECOSYSTEM:introduced=0.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a hosted service.
- Am I affected?
- Check whether you run motioneye (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an OS command injection flaw (CWE-20) in configuration parameter handling. User-supplied input in parameters such as image_file_name is written directly to motion configuration files without sanitization. An authenticated attacker with admin privileges can inject shell metacharacters and commands into these parameters. When the motion daemon restarts, it executes the injected commands with the privileges of the motion process, achieving arbitrary code execution. The attack requires authentication and admin access, and code execution occurs only upon motion service restart. Versions up to 0.43.1b4 are affected; the advisory was withdrawn as a duplicate of GHSA-j945-qm58-4gjx.
Affected products
- motionEye motionEye 0.43.1b4 and earlier
Timeline
- 2025-10-03: disclosed
- 2025-11-03: other: Advisory withdrawn as duplicate of GHSA-j945-qm58-4gjx