Quick answers
- Is CVE-2022-25568 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-25568 being exploited in the wild.
- How severe is CVE-2022-25568?
- Low severity, with a CVSS score of 3.1, published 24 March 2022.
- Which products and versions are affected?
- motioneye (PyPI) ECOSYSTEM:introduced=0,fixed=0.43.1b1.
- Is there a fix for CVE-2022-25568?
- Yes. motioneye (PyPI): upgrade to 0.43.1b1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-25568 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2022-25568?
- 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.
How to fix
- motioneye (PyPI): upgrade to 0.43.1b1 or later
pip install "motioneye>=0.43.1b1"
Technical details
MotionEye versions 0.42.1 and earlier contain an information disclosure vulnerability (CWE-200) in the /config/list endpoint. The vulnerability allows unauthenticated attackers to access sensitive configuration data via a GET request when no regular user password is configured. The attack requires no authentication and is trivial to execute over the network. Exploitation exposes system configuration details that could aid further reconnaissance. The vulnerability is fixed in version 0.43.1b1.
Affected products
- MotionEye Project MotionEye 0.42.1 and earlier
Identifiers
- CVE-2022-25568
- GHSA-2c7w-v459-cwgf
- PYSEC-2022-43141
Timeline
- 2022-03-25: disclosed
- 2022: patched: Fixed in version 0.43.1b1