CVE-2026-32315: CWE-732: Incorrect Permission Assignment for Critical Resource in motioneye-project motioneye
motionEye (mEye) is an online interface for motion software, a video surveillance program with motion detection. Versions prior to 0.44.0 create the configuration file /etc/motioneye/motion.conf with 644 permissions (-rw-r--r--), making it readable by any local user on the system. This file contains sensitive data including the admin password hash, which can be leveraged by other vulnerabilities to escalate privileges. Additionally, per-camera configuration files (camera-*.conf) are also created with the same 644 permissions, potentially exposing camera-specific credentials and settings. The exposed SHA1 admin password hash can be cracked offline to recover the plaintext password, used directly to forge authenticated admin API requests via the signature authentication weakness (GHSA-45h7-499j-7ww3), and chained with the OS command injection flaw (CVE-2025-60787) to escalate a local unprivileged user to the Motion daemon user (often root), enabling full system compromise. This issue has been fixed in version 0.44.0.
AI Analysis
Technical Summary
motionEye (mEye) is a video surveillance interface that, before version 0.44.0, sets the configuration file /etc/motioneye/motion.conf and per-camera configuration files (camera-*.conf) with 644 permissions, making them readable by any local user. These files contain sensitive information including the SHA1 admin password hash and camera credentials. The exposed admin password hash can be cracked offline to recover the plaintext password. This password can then be used to forge authenticated admin API requests due to a signature authentication weakness (GHSA-45h7-499j-7ww3) and combined with an OS command injection vulnerability (CVE-2025-60787) to escalate a local unprivileged user to the Motion daemon user, often root, leading to full system compromise. The vulnerability is resolved in motionEye version 0.44.0.
Potential Impact
Local users on affected systems can read sensitive configuration files containing the admin password hash and camera credentials due to incorrect file permissions. The exposed SHA1 hash can be cracked offline, allowing attackers to recover the admin password. This can be leveraged to forge authenticated API requests and, when chained with other vulnerabilities, escalate privileges to root, resulting in full system compromise.
Mitigation Recommendations
Upgrade motionEye to version 0.44.0 or later, where the issue is fixed by correcting file permissions on configuration files. No other mitigation is necessary as the fix addresses the root cause of the vulnerability.
CVE-2026-32315: CWE-732: Incorrect Permission Assignment for Critical Resource in motioneye-project motioneye
Description
motionEye (mEye) is an online interface for motion software, a video surveillance program with motion detection. Versions prior to 0.44.0 create the configuration file /etc/motioneye/motion.conf with 644 permissions (-rw-r--r--), making it readable by any local user on the system. This file contains sensitive data including the admin password hash, which can be leveraged by other vulnerabilities to escalate privileges. Additionally, per-camera configuration files (camera-*.conf) are also created with the same 644 permissions, potentially exposing camera-specific credentials and settings. The exposed SHA1 admin password hash can be cracked offline to recover the plaintext password, used directly to forge authenticated admin API requests via the signature authentication weakness (GHSA-45h7-499j-7ww3), and chained with the OS command injection flaw (CVE-2025-60787) to escalate a local unprivileged user to the Motion daemon user (often root), enabling full system compromise. This issue has been fixed in version 0.44.0.
CVSS v3.1
Score 5.5medium
Affected software
pkg:github/motioneye-project/motioneyeRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
motionEye (mEye) is a video surveillance interface that, before version 0.44.0, sets the configuration file /etc/motioneye/motion.conf and per-camera configuration files (camera-*.conf) with 644 permissions, making them readable by any local user. These files contain sensitive information including the SHA1 admin password hash and camera credentials. The exposed admin password hash can be cracked offline to recover the plaintext password. This password can then be used to forge authenticated admin API requests due to a signature authentication weakness (GHSA-45h7-499j-7ww3) and combined with an OS command injection vulnerability (CVE-2025-60787) to escalate a local unprivileged user to the Motion daemon user, often root, leading to full system compromise. The vulnerability is resolved in motionEye version 0.44.0.
Potential Impact
Local users on affected systems can read sensitive configuration files containing the admin password hash and camera credentials due to incorrect file permissions. The exposed SHA1 hash can be cracked offline, allowing attackers to recover the admin password. This can be leveraged to forge authenticated API requests and, when chained with other vulnerabilities, escalate privileges to root, resulting in full system compromise.
Mitigation Recommendations
Upgrade motionEye to version 0.44.0 or later, where the issue is fixed by correcting file permissions on configuration files. No other mitigation is necessary as the fix addresses the root cause of the vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-11T21:16:21.660Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3c4ce14853345fc1df8ce1
Added to database: 06/24/2026, 21:32:17 UTC
Last enriched: 07/01/2026, 22:46:17 UTC
Last updated: 08/09/2026, 00:41:13 UTC
Views: 93
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.