PYSEC-2019-104

Vulnerability from pysec - Published: 2019-08-18 20:15 - Updated: 2019-08-30 11:38
VLAI?
Details

** DISPUTED ** 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.

Impacted products
Name purl
mitogen pkg:pypi/mitogen

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "mitogen",
        "purl": "pkg:pypi/mitogen"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5924af1566763e48c42028399ea0cd95c457b3dc"
            }
          ],
          "repo": "https://github.com/dw/mitogen",
          "type": "GIT"
        },
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.2.8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.2.0",
        "0.2.1",
        "0.2.2",
        "0.2.3",
        "0.2.4",
        "0.2.5",
        "0.2.6",
        "0.2.7"
      ]
    }
  ],
  "aliases": [
    "CVE-2019-15149",
    "GHSA-8rf6-w2mx-4xjh"
  ],
  "details": "** DISPUTED ** 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.",
  "id": "PYSEC-2019-104",
  "modified": "2019-08-30T11:38:00Z",
  "published": "2019-08-18T20:15:00Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://mitogen.networkgenomics.com/changelog.html#v0-2-8-2019-08-18"
    },
    {
      "type": "FIX",
      "url": "https://github.com/dw/mitogen/commit/5924af1566763e48c42028399ea0cd95c457b3dc"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-8rf6-w2mx-4xjh"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…