{"answers":{"affected":"3 open source packages ship an affected version, including motioneye. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25568 exists.","fix":"Upgrade motioneye to 0.43.1b1 or later.","what":"CVE-2022-25568 is a high-severity vulnerability in n/a, published on 24 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-25568 and fix it if it is affected.\n\nWhat it is: CVE-2022-25568 is a high-severity vulnerability in n/a, published on 24 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25568 exists.\n\nAffected packages and fixed versions:\n- motioneye (PyPI): affected all versions; fixed in 0.43.1b1\n- motioneye (PyPI): affected all versions; fixed in 0.43.1b1\n- motioneye (PyPI): affected all versions; fixed in 0.43.1b1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-25568/ (Markdown: https://insights.sbomify.com/CVE-2022-25568/index.md)","id":"CVE-2022-25568","markdown":"https://insights.sbomify.com/CVE-2022-25568/index.md","name":"CVE-2022-25568","record":{"aliases":["GHSA-2c7w-v459-cwgf","PYSEC-2022-43141"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"MotionEye web interface","requires_auth":"none","summary":"Attackers can access sensitive configuration data via an unauthenticated GET request if the regular user password is not configured.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"motioneye","vendor":"motioneye_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2022/CVE-2022-25568.yaml","stars":null,"title":"MotionEye Config Info Disclosure"}],"tier":"weaponised"},"has_fix":true,"headline":"MotionEye allows attackers to access sensitive information","id":"CVE-2022-25568","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":3,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-25569"},"packages":[{"ecosystem":"PyPI","fixed":["0.43.1b1"],"introduced":["0"],"last_affected":[],"package":"motioneye","purl":null,"source":"GHSA-2c7w-v459-cwgf"},{"ecosystem":"PyPI","fixed":["0.43.1b1"],"introduced":["0"],"last_affected":[],"package":"motioneye","purl":"pkg:pypi/motioneye","source":"GHSA-2c7w-v459-cwgf"},{"ecosystem":"PyPI","fixed":["0.43.1b1"],"introduced":["0"],"last_affected":[],"package":"motioneye","purl":"pkg:pypi/motioneye","source":"PYSEC-2022-43141"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-25566"},"products":["n/a"],"published":"2022-03-24","related":[{"cvss_score":7.2,"headline":"motionEye vulnerable to RCE via unsanitized motion config parameter","id":"CVE-2025-60787","kev_date_added":null,"published":"2025-10-03"},{"cvss_score":7.2,"headline":"Unrestricted Upload of File with Dangerous Type in motionEye","id":"CVE-2021-44255","kev_date_added":null,"published":"2022-01-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can access sensitive configuration data via an unauthenticated GET request if the regular user password is not configured.","url":"https://insights.sbomify.com/CVE-2022-25568/"}