PYSEC-2017-28

Vulnerability from pysec - Published: 2017-01-23 21:59 - Updated: 2021-07-05 00:01
VLAI?
Details

python-jose before 1.3.2 allows attackers to have unspecified impact by leveraging failure to use a constant time comparison for HMAC keys.

Impacted products
Name purl
python-jose pkg:pypi/python-jose
Aliases

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "python-jose",
        "purl": "pkg:pypi/python-jose"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.3.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.1.0",
        "0.1.1",
        "0.1.2",
        "0.1.3",
        "0.1.4",
        "0.1.5",
        "0.1.6",
        "0.1.7",
        "0.1.8",
        "0.2.0",
        "0.3.0",
        "0.4.0",
        "0.5.0",
        "0.5.1",
        "0.5.2",
        "0.5.3",
        "0.5.4",
        "0.5.5",
        "0.5.6",
        "0.6.1",
        "0.6.2",
        "0.7.0",
        "1.0.0",
        "1.1.0",
        "1.2.0",
        "1.3.0",
        "1.3.1"
      ]
    }
  ],
  "aliases": [
    "CVE-2016-7036"
  ],
  "details": "python-jose before 1.3.2 allows attackers to have unspecified impact by leveraging failure to use a constant time comparison for HMAC keys.",
  "id": "PYSEC-2017-28",
  "modified": "2021-07-05T00:01:25.423622Z",
  "published": "2017-01-23T21:59:00Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/mpdavis/python-jose/releases/tag/1.3.2"
    },
    {
      "type": "WEB",
      "url": "https://github.com/mpdavis/python-jose/pull/35/commits/89b46353b9f611e9da38de3d2fedf52331167b93"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/95845"
    }
  ]
}


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…