{"answers":{"affected":"3 open source packages ship an affected version, including motioneye. It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-44255 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-44255 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-44255 is a high-severity unsafe deserialization vulnerability in n/a, published on 31 Jan 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-44255 and fix it if it is affected.\n\nWhat it is: CVE-2021-44255 is a high-severity unsafe deserialization vulnerability in n/a, published on 31 Jan 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-44255 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- motioneye (PyPI): affected all versions up to 0.42.1; no fix listed\n- motioneye (PyPI): affected all versions up to 0.42.1; no fix listed\n- motioneye (PyPI): affected all versions up to 0.42.1; no fix listed\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-2021-44255/ (Markdown: https://insights.sbomify.com/CVE-2021-44255/index.md)","id":"CVE-2021-44255","markdown":"https://insights.sbomify.com/CVE-2021-44255/index.md","name":"CVE-2021-44255","record":{"aliases":["GHSA-m2c7-42rf-c62f","PYSEC-2026-681"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"MotionEye web interface","requires_auth":"high_privilege","summary":"Authenticated attackers can achieve remote code execution by uploading a malicious configuration backup containing a Python pickle file.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"motioneye","vendor":"motioneye_project"},{"product":"motioneyeos","vendor":"motioneyeos_project"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Authenticated remote code execution in MotionEye \u003c= 0.42.1 and MotioneEyeOS \u003c= 20200606 allows a remote attacker to upload a configuration backup file containing a malicious python pickle file which will execute arbitrary code on the server.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":"2021-10-22","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2021-10-22T16:15:08Z","kind":"github_poc","ref":"https://github.com/pizza-power/motioneye-authenticated-RCE","stars":1,"title":"A Python 3 script that uploads a tasks.pickle file that enables RCE in MotionEye. CVE-2021-44255"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Unrestricted Upload of File with Dangerous Type in motionEye","id":"CVE-2021-44255","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2021"},"n_packages":3,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2021-44259"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.42.1"],"package":"motioneye","purl":null,"source":"GHSA-m2c7-42rf-c62f"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.42.1"],"package":"motioneye","purl":"pkg:pypi/motioneye","source":"GHSA-m2c7-42rf-c62f"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.42.1"],"package":"motioneye","purl":"pkg:pypi/motioneye","source":"PYSEC-2026-681"}],"prev":{"headline":"SQL injection in n/a","id":"CVE-2021-44249"},"products":["n/a"],"published":"2022-01-31","related":[{"cvss_score":7.5,"headline":"MotionEye allows attackers to access sensitive information","id":"CVE-2022-25568","kev_date_added":null,"published":"2022-03-24"},{"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"}],"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":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Authenticated attackers can achieve remote code execution by uploading a malicious configuration backup containing a Python pickle file.","url":"https://insights.sbomify.com/CVE-2021-44255/"}