pysec-2012-20
Vulnerability from pysec
Published
2012-12-18 01:55
Modified
2023-11-07 20:24
Details

OpenStack Keystone, as used in OpenStack Folsom 2012.2, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by creating new tokens through token chaining. NOTE: this issue exists because of a CVE-2012-3426 regression.

Aliases



{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "keystone",
        "purl": "pkg:pypi/keystone"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "38c7e46a640a94da4da89a39a5a1ea9c081f1eb5"
            },
            {
              "fixed": "f9d4766249a72d8f88d75dcf1575b28dd3496681"
            }
          ],
          "repo": "https://github.com/openstack/keystone",
          "type": "GIT"
        },
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "12.0.2",
        "12.0.3",
        "13.0.2",
        "13.0.3",
        "13.0.4",
        "14.0.0",
        "14.0.1",
        "14.1.0",
        "14.2.0",
        "15.0.0",
        "15.0.0.0rc1",
        "15.0.0.0rc2",
        "15.0.1",
        "16.0.0",
        "16.0.0.0rc1",
        "16.0.0.0rc2",
        "16.0.1",
        "16.0.2",
        "17.0.0",
        "17.0.0.0rc1",
        "17.0.0.0rc2",
        "17.0.1",
        "18.0.0",
        "18.0.0.0rc1",
        "18.1.0",
        "19.0.0",
        "19.0.0.0rc1",
        "19.0.0.0rc2",
        "19.0.1",
        "20.0.0",
        "20.0.0.0rc1",
        "20.0.1",
        "21.0.0",
        "21.0.0.0rc1",
        "21.0.1",
        "22.0.0",
        "22.0.0.0rc1",
        "22.0.1",
        "23.0.0",
        "23.0.0.0rc1",
        "23.0.1",
        "24.0.0",
        "24.0.0.0rc1"
      ]
    }
  ],
  "aliases": [
    "CVE-2012-5563"
  ],
  "details": "OpenStack Keystone, as used in OpenStack Folsom 2012.2, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by creating new tokens through token chaining.  NOTE: this issue exists because of a CVE-2012-3426 regression.",
  "id": "PYSEC-2012-20",
  "modified": "2023-11-07T20:24:25.260316+00:00",
  "published": "2012-12-18T01:55:00+00:00",
  "references": [
    {
      "type": "WEB",
      "url": "https://bugs.launchpad.net/keystone/+bug/1079216"
    },
    {
      "type": "ADVISORY",
      "url": "http://www.ubuntu.com/usn/USN-1641-1"
    },
    {
      "type": "ADVISORY",
      "url": "http://secunia.com/advisories/51436"
    },
    {
      "type": "ADVISORY",
      "url": "http://secunia.com/advisories/51423"
    },
    {
      "type": "FIX",
      "url": "https://github.com/openstack/keystone/commit/38c7e46a640a94da4da89a39a5a1ea9c081f1eb5"
    },
    {
      "type": "FIX",
      "url": "https://github.com/openstack/keystone/commit/f9d4766249a72d8f88d75dcf1575b28dd3496681"
    },
    {
      "type": "FIX",
      "url": "http://www.openwall.com/lists/oss-security/2012/11/28/5"
    },
    {
      "type": "FIX",
      "url": "http://www.openwall.com/lists/oss-security/2012/11/28/6"
    },
    {
      "type": "ADVISORY",
      "url": "http://rhn.redhat.com/errata/RHSA-2012-1557.html"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/56727"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/80370"
    }
  ]
}


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.