CVE-2022-25568
Published: 24 March 2022
Summary
CVE-2022-25568 is a high-severity Initialization of a Resource with an Insecure Default (CWE-1188) vulnerability in Motioneye Project Motioneye. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 0.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
MotionEye versions 0.42.1 and earlier contain an information disclosure vulnerability tracked as CVE-2022-25568. The flaw resides in the web interface and permits unauthenticated retrieval of sensitive configuration data through a simple GET request to the /config/list endpoint. Exploitation is possible only when no password has been configured for the regular user account, leaving the instance in an insecure default state covered by CWE-1188.
An attacker with network access can issue the request without credentials or user interaction and obtain high-value configuration details. The CVSS 7.5 score reflects the combination of remote attack vector, low complexity, and complete loss of confidentiality while integrity and availability remain unaffected.
Public references, including the upstream GitHub issue and a technical write-up published in February 2022, describe the exposure and note that setting a regular user password prevents the endpoint from returning data. No official patch release or coordinated advisory from the MotionEye project is referenced in the available sources.
The CVE carries an EPSS score that reached a peak of 0.8977 and currently stands at 0.8531, indicating sustained exploitation interest after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-0402
Vulnerability details
MotionEye v0.42.1 and below allows attackers to access sensitive information via a GET request to /config/list. To exploit this vulnerability, a regular user password must be unconfigured.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requires documented secure initialization practices and avoidance of insecure defaults in configuration baselines.
Reviewing and updating baseline when components are installed or upgraded prevents initialization with insecure defaults.
Requiring explicit configuration to minimal functionality overrides insecure defaults that would otherwise enable excess capabilities.
Tailoring replaces or augments insecure default initializations with system-specific values and compensating controls before deployment.
Central configuration overrides or replaces insecure default initializations that would otherwise be left unchanged on each system.
SCRM practices during acquisition and configuration management address insecure default initializations shipped by vendors.
Scans detect resources initialized with insecure defaults that create exploitable conditions.
Instruction on secure initialization of security controls prevents leaving resources with insecure defaults after installation.