PYSEC-2011-22

Vulnerability from pysec - Published: 2011-12-30 01:55 - Updated: 2021-08-27 03:22
VLAI?
Details

Plone 4.1.3 and earlier computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

Impacted products
Name purl
plone pkg:pypi/plone
Aliases
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "plone",
        "purl": "pkg:pypi/plone"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.1.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.2",
        "3.2.1",
        "3.2.2",
        "3.2.3",
        "3.2a1",
        "3.2rc1",
        "3.3",
        "3.3.1",
        "3.3.2",
        "3.3.3",
        "3.3.4",
        "3.3.5",
        "3.3.6",
        "3.3b1",
        "3.3rc1",
        "3.3rc2",
        "3.3rc3",
        "3.3rc4",
        "3.3rc5",
        "4.0",
        "4.0.1",
        "4.0.10",
        "4.0.2",
        "4.0.3",
        "4.0.4",
        "4.0.5",
        "4.0.6",
        "4.0.7",
        "4.0.8",
        "4.0.9",
        "4.0a1",
        "4.0a2",
        "4.0a3",
        "4.0a4",
        "4.0a5",
        "4.0b1",
        "4.0b2",
        "4.0b3",
        "4.0b4",
        "4.0b5",
        "4.0rc1",
        "4.1",
        "4.1.1",
        "4.1.2",
        "4.1.3",
        "4.1a1",
        "4.1a2",
        "4.1a3",
        "4.1b1",
        "4.1b2",
        "4.1rc2",
        "4.1rc3"
      ]
    }
  ],
  "aliases": [
    "CVE-2011-4462",
    "GHSA-pcwm-8jc3-qxvj"
  ],
  "details": "Plone 4.1.3 and earlier computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.",
  "id": "PYSEC-2011-22",
  "modified": "2021-08-27T03:22:11.387960Z",
  "published": "2011-12-30T01:55:00Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "http://www.nruns.com/_downloads/advisory28122011.pdf"
    },
    {
      "type": "WEB",
      "url": "http://www.kb.cert.org/vuls/id/903934"
    },
    {
      "type": "ADVISORY",
      "url": "http://www.ocert.org/advisories/ocert-2011-003.html"
    },
    {
      "type": "ADVISORY",
      "url": "http://secunia.com/advisories/47406"
    },
    {
      "type": "WEB",
      "url": "http://archives.neohapsis.com/archives/bugtraq/2011-12/0181.html"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/72018"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-pcwm-8jc3-qxvj"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.



Detection rules are retrieved from Rulezet.