PYSEC-2016-39

Vulnerability from pysec - Published: 2016-12-23 22:59 - Updated: 2024-11-21 14:23
VLAI?
Details

An exploitable out-of-bounds array access vulnerability exists in the xrow_header_decode function of Tarantool 1.7.2.0-g8e92715. A specially crafted packet can cause the function to access an element outside the bounds of a global array that is used to determine the type of the specified key's value. This can lead to an out of bounds read within the context of the server. An attacker who exploits this vulnerability can cause a denial of service vulnerability on the server.

Impacted products
Name purl
tarantool pkg:pypi/tarantool
Aliases

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "tarantool",
        "purl": "pkg:pypi/tarantool"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.10.0",
        "0.11.0",
        "0.12.0",
        "0.12.1",
        "0.3.0",
        "0.3.2",
        "0.3.3",
        "0.3.4",
        "0.3.5",
        "0.3.6",
        "0.5.0",
        "0.5.1",
        "0.5.2",
        "0.5.3",
        "0.5.4",
        "0.5.5",
        "0.6.1",
        "0.6.2",
        "0.6.3",
        "0.6.4",
        "0.6.5",
        "0.6.6",
        "0.7.0",
        "0.7.1",
        "0.8.0",
        "0.9.0",
        "1.0.0",
        "1.1.0",
        "1.1.1",
        "1.1.2",
        "1.2.0"
      ]
    }
  ],
  "aliases": [
    "CVE-2016-9037"
  ],
  "details": "An exploitable out-of-bounds array access vulnerability exists in the xrow_header_decode function of Tarantool 1.7.2.0-g8e92715. A specially crafted packet can cause the function to access an element outside the bounds of a global array that is used to determine the type of the specified key\u0027s value. This can lead to an out of bounds read within the context of the server. An attacker who exploits this vulnerability can cause a denial of service vulnerability on the server.",
  "id": "PYSEC-2016-39",
  "modified": "2024-11-21T14:23:01.531112Z",
  "published": "2016-12-23T22:59:00Z",
  "references": [
    {
      "type": "EVIDENCE",
      "url": "http://www.talosintelligence.com/reports/TALOS-2016-0255/"
    },
    {
      "type": "WEB",
      "url": "http://www.talosintelligence.com/reports/TALOS-2016-0255/"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/95063"
    },
    {
      "type": "ADVISORY",
      "url": "http://www.securityfocus.com/bid/95063"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "withdrawn": "2024-11-22T04:37:05Z"
}


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…