{"answers":{"affected":"3 open source packages ship an affected version, including mitogen. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15149 in the wild and no public exploit code.","fix":"Upgrade mitogen to 0.2.8 or later.","what":"CVE-2019-15149 is a critical vulnerability in n/a, published on 18 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15149 and fix it if it is affected.\n\nWhat it is: CVE-2019-15149 is a critical vulnerability in n/a, published on 18 Aug 2019. 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-2019-15149 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mitogen (PyPI): affected all versions; fixed in 0.2.8\n- mitogen (PyPI): affected all versions; fixed in 0.2.8\n- mitogen (PyPI): affected all versions; fixed in 0.2.8\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-15149/ (Markdown: https://insights.sbomify.com/CVE-2019-15149/index.md)","id":"CVE-2019-15149","markdown":"https://insights.sbomify.com/CVE-2019-15149/index.md","name":"CVE-2019-15149","record":{"aliases":["GHSA-8rf6-w2mx-4xjh","PYSEC-2019-104"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Python library","requires_auth":"none","summary":"A typo in Mitogen disables routing protection for child-initiated connections, potentially allowing security bypass if combined with other specific bugs.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mitogen","vendor":"networkgenomics"}],"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-254","name":null}],"description":"core.py in Mitogen before 0.2.8 has a typo that drops the unidirectional-routing protection mechanism in the case of a child that is initiated by another child. The Ansible extension is unaffected. NOTE: the vendor disputes this issue because it is exploitable only in conjunction with hypothetical other factors, i.e., an affected use case within a library caller, and a bug in the message receiver policy code that led to reliance on this extra protection mechanism","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":"Undirectional routing wasn't respected in some cases in Mitogen","id":"CVE-2019-15149","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":3,"n_references":2,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-15150"},"packages":[{"ecosystem":"PyPI","fixed":["0.2.8"],"introduced":["0"],"last_affected":[],"package":"mitogen","purl":null,"source":"GHSA-8rf6-w2mx-4xjh"},{"ecosystem":"PyPI","fixed":["0.2.8"],"introduced":["0"],"last_affected":[],"package":"mitogen","purl":"pkg:pypi/mitogen","source":"GHSA-8rf6-w2mx-4xjh"},{"ecosystem":"PyPI","fixed":["0.2.8"],"introduced":["0"],"last_affected":[],"package":"mitogen","purl":"pkg:pypi/mitogen","source":"PYSEC-2019-104"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-15148"},"products":["n/a"],"published":"2019-08-18","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":"A typo in Mitogen disables routing protection for child-initiated connections, potentially allowing security bypass if combined with other specific bugs.","url":"https://insights.sbomify.com/CVE-2019-15149/"}