{"answers":{"affected":"5 open source packages ship an affected version, including nameko. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41078 in the wild and no public exploit code.","fix":"Upgrade nameko to a fixed version for your release line: 2.14.0 or 3.0.0rc10.","what":"CVE-2021-41078 is a high-severity unsafe deserialization vulnerability in n/a, published on 26 Oct 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-41078 and fix it if it is affected.\n\nWhat it is: CVE-2021-41078 is a high-severity unsafe deserialization vulnerability in n/a, published on 26 Oct 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-41078 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nameko (PyPI): affected all versions; fixed in 2.14.0\n- nameko (PyPI): affected all versions; fixed in 2.14.0\n- nameko (PyPI): affected all versions; fixed in 2.14.0\n- nameko (PyPI): affected from 3.0.0rc0; fixed in 3.0.0rc10\n- nameko (PyPI): affected from 3.0.0rc0; fixed in 3.0.0rc10\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-41078/ (Markdown: https://insights.sbomify.com/CVE-2021-41078/index.md)","id":"CVE-2021-41078","markdown":"https://insights.sbomify.com/CVE-2021-41078/index.md","name":"CVE-2021-41078","record":{"aliases":["GHSA-6p52-jr3q-c94g","PYSEC-2021-383"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python microservices framework","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking Nameko into deserializing a malicious configuration file.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nameko","vendor":"nameko"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"Nameko through 2.13.0 can be tricked into performing arbitrary code execution when deserializing the config file.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":"2022-08-28","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-08-28T06:42:59Z","kind":"github_poc","ref":"https://github.com/s-index/CVE-2021-41078","stars":0,"title":"nameko Arbitrary code execution due to YAML deserialization"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Nameko Arbitrary code execution due to YAML deserialization","id":"CVE-2021-41078","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2021"},"n_packages":5,"n_references":2,"next":{"headline":"Apache Tomcat DoS with unexpected TLS packet","id":"CVE-2021-41079"},"packages":[{"ecosystem":"PyPI","fixed":["2.14.0"],"introduced":["0"],"last_affected":[],"package":"nameko","purl":null,"source":"GHSA-6p52-jr3q-c94g"},{"ecosystem":"PyPI","fixed":["2.14.0"],"introduced":["0"],"last_affected":[],"package":"nameko","purl":"pkg:pypi/nameko","source":"GHSA-6p52-jr3q-c94g"},{"ecosystem":"PyPI","fixed":["2.14.0"],"introduced":["0"],"last_affected":[],"package":"nameko","purl":"pkg:pypi/nameko","source":"PYSEC-2021-383"},{"ecosystem":"PyPI","fixed":["3.0.0rc10"],"introduced":["3.0.0rc0"],"last_affected":[],"package":"nameko","purl":null,"source":"GHSA-6p52-jr3q-c94g"},{"ecosystem":"PyPI","fixed":["3.0.0rc10"],"introduced":["3.0.0rc0"],"last_affected":[],"package":"nameko","purl":"pkg:pypi/nameko","source":"GHSA-6p52-jr3q-c94g"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2021-41077"},"products":["n/a"],"published":"2021-10-26","related":[],"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":"Attackers can execute arbitrary code by tricking Nameko into deserializing a malicious configuration file.","url":"https://insights.sbomify.com/CVE-2021-41078/"}