pysec-2020-343
Vulnerability from pysec
Published
2020-11-27 20:15
Modified
2024-12-12 14:22
Severity ?
7.8 (High) - CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Details

blosc2.c in Blosc C-Blosc2 through 2.0.0.beta.5 has a heap-based buffer overflow when there is a lack of space to write compressed data.

Impacted products
Name purl
blosc2 pkg:pypi/blosc2
Aliases


To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "blosc2",
            purl: "pkg:pypi/blosc2",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "c4c6470e88210afc95262c8b9fcc27e30ca043ee",
                  },
               ],
               repo: "https://github.com/Blosc/c-blosc2",
               type: "GIT",
            },
            {
               events: [
                  {
                     introduced: "0",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "0.1.1",
            "0.1.10",
            "0.1.2",
            "0.1.3",
            "0.1.4",
            "0.1.5",
            "0.1.6",
            "0.1.7",
            "0.1.8",
            "0.1.9",
            "0.2.0",
            "0.3.0",
            "0.3.1",
            "0.3.2",
            "0.4.0",
            "0.4.1",
            "0.5.1",
            "0.5.2",
            "0.6.1",
            "0.6.2",
            "0.6.3",
            "0.6.4",
            "0.6.5",
            "0.6.6",
            "2.0.0",
            "2.1.0",
            "2.1.1",
            "2.2.0",
            "2.2.1",
            "2.2.2",
            "2.2.3",
            "2.2.4",
            "2.2.5",
            "2.2.6",
            "2.2.7",
            "2.2.8",
            "2.2.9",
            "2.3.0",
            "2.3.1",
            "2.3.2",
            "2.4.0",
            "2.5.0",
            "2.5.1",
            "2.6.0",
            "2.6.1",
            "2.6.2",
            "2.7.0",
            "2.7.1",
            "3.0.0b1",
            "3.0.0b3",
            "3.0.0b4",
            "3.0.0rc1",
            "3.0.0rc2",
            "3.0.0rc3",
            "3.0.0",
         ],
      },
   ],
   aliases: [
      "CVE-2020-29367",
   ],
   details: "blosc2.c in Blosc C-Blosc2 through 2.0.0.beta.5 has a heap-based buffer overflow when there is a lack of space to write compressed data.",
   id: "PYSEC-2020-343",
   modified: "2024-12-12T14:22:45.450508Z",
   published: "2020-11-27T20:15:00Z",
   references: [
      {
         type: "FIX",
         url: "https://github.com/Blosc/c-blosc2/commit/c4c6470e88210afc95262c8b9fcc27e30ca043ee",
      },
      {
         type: "ARTICLE",
         url: "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26442",
      },
      {
         type: "WEB",
         url: "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26442",
      },
   ],
   severity: [
      {
         score: "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
         type: "CVSS_V3",
      },
   ],
   withdrawn: "2024-11-22T04:37:03Z",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




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.