pysec-2021-13
Vulnerability from pysec
Published
2021-05-13 23:15
Modified
2023-07-25 00:34
Details

The Flask-Caching extension through 1.10.1 for Flask relies on Pickle for serialization, which may lead to remote code execution or local privilege escalation. If an attacker gains access to cache storage (e.g., filesystem, Memcached, Redis, etc.), they can construct a crafted payload, poison the cache, and execute Python code.




{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "flask-caching",
        "purl": "pkg:pypi/flask-caching"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.0.0",
        "1.0.1",
        "1.1.0",
        "1.1.1",
        "1.2.0",
        "1.3.0",
        "1.3.1",
        "1.3.2",
        "1.3.3",
        "1.4.0",
        "1.5.0",
        "1.6.0",
        "1.7.0",
        "1.7.1",
        "1.7.2",
        "1.8.0",
        "1.9.0",
        "1.10.0",
        "1.10.1",
        "1.11.0",
        "1.11.1",
        "2.0.0",
        "2.0.1",
        "2.0.2"
      ]
    }
  ],
  "aliases": [
    "CVE-2021-33026",
    "GHSA-656c-6cxf-hvcv"
  ],
  "details": "The Flask-Caching extension through 1.10.1 for Flask relies on Pickle for serialization, which may lead to remote code execution or local privilege escalation. If an attacker gains access to cache storage (e.g., filesystem, Memcached, Redis, etc.), they can construct a crafted payload, poison the cache, and execute Python code.",
  "id": "PYSEC-2021-13",
  "modified": "2023-07-25T00:34:15.721702Z",
  "published": "2021-05-13T23:15:00Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/sh4nks/flask-caching/pull/209"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-656c-6cxf-hvcv"
    }
  ],
  "withdrawn": "2023-07-25T12:32:00Z"
}


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 seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.