{"answers":{"affected":"3 open source packages ship an affected version, including definitions. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20325 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20325 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20325 is a critical code injection vulnerability in n/a, published on 21 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-20325 and fix it if it is affected.\n\nWhat it is: CVE-2018-20325 is a critical code injection vulnerability in n/a, published on 21 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-20325 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- definitions (PyPI): affected all versions; no fix listed\n- definitions (PyPI): affected all versions up to 0.2.0; no fix listed\n- definitions (PyPI): affected all versions up to 0.2.0; 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-2018-20325/ (Markdown: https://insights.sbomify.com/CVE-2018-20325/index.md)","id":"CVE-2018-20325","markdown":"https://insights.sbomify.com/CVE-2018-20325/index.md","name":"CVE-2018-20325","record":{"aliases":["GHSA-v4x4-98cg-wr4g","PYSEC-2018-82"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python definitions package","requires_auth":"none","summary":"Attackers can execute arbitrary Python commands via the load method in the definitions package, potentially compromising the host system.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"definitions","vendor":"definitions_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"There is a vulnerability in load() method in definitions/parser.py in the Danijar Hafner definitions package for Python. It can execute arbitrary python commands resulting in command execution.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Code injection in Danijar Definitions","id":"CVE-2018-20325","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2018"},"n_packages":3,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-20326"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":[],"package":"definitions","purl":"pkg:pypi/definitions","source":"PYSEC-2018-82"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"definitions","purl":null,"source":"GHSA-v4x4-98cg-wr4g"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"definitions","purl":"pkg:pypi/definitions","source":"GHSA-v4x4-98cg-wr4g"}],"prev":{"headline":"Command injection in n/a","id":"CVE-2018-20323"},"products":["n/a"],"published":"2018-12-21","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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can execute arbitrary Python commands via the load method in the definitions package, potentially compromising the host system.","url":"https://insights.sbomify.com/CVE-2018-20325/"}