{"answers":{"affected":"3 open source packages ship an affected version, including sqla-yaml-fixtures. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-3575 in the wild and no public exploit code.","fix":"Upgrade sqla-yaml-fixtures to 1.0.0 or later.","what":"CVE-2019-3575 is a high-severity code injection vulnerability in n/a, published on 3 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-3575 and fix it if it is affected.\n\nWhat it is: CVE-2019-3575 is a high-severity code injection vulnerability in n/a, published on 3 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-3575 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sqla-yaml-fixtures (PyPI): affected all versions up to 0.9.1; no fix listed\n- sqla-yaml-fixtures (PyPI): affected all versions up to 0.9.1; no fix listed\n- sqla-yaml-fixtures (PyPI): affected all versions; fixed in 1.0.0\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-2019-3575/ (Markdown: https://insights.sbomify.com/CVE-2019-3575/index.md)","id":"CVE-2019-3575","markdown":"https://insights.sbomify.com/CVE-2019-3575/index.md","name":"CVE-2019-3575","record":{"aliases":["GHSA-2x54-j4m3-r6wx","PYSEC-2019-122"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python YAML fixtures library","requires_auth":"low_privilege","summary":"Local attackers can execute arbitrary Python code via the fixture_text argument in the sqla_yaml_fixtures library.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sqla_yaml_fixtures","vendor":"sqla_yaml_fixtures_project"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/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":"Sqla_yaml_fixtures 0.9.1 allows local users to execute arbitrary python code via the fixture_text argument in sqla_yaml_fixtures.load.","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":true,"headline":"sqla-yaml-fixtures is vulnerable to Code Injection","id":"CVE-2019-3575","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":3,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2019-3576"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.9.1"],"package":"sqla-yaml-fixtures","purl":null,"source":"GHSA-2x54-j4m3-r6wx"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.9.1"],"package":"sqla-yaml-fixtures","purl":"pkg:pypi/sqla-yaml-fixtures","source":"GHSA-2x54-j4m3-r6wx"},{"ecosystem":"PyPI","fixed":["1.0.0"],"introduced":["0"],"last_affected":[],"package":"sqla-yaml-fixtures","purl":"pkg:pypi/sqla-yaml-fixtures","source":"PYSEC-2019-122"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-3574"},"products":["n/a"],"published":"2019-01-03","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-04","vendors":["n/a"]},"summary":"Local attackers can execute arbitrary Python code via the fixture_text argument in the sqla_yaml_fixtures library.","url":"https://insights.sbomify.com/CVE-2019-3575/"}