osv-2020-2239
Vulnerability from osv_ossfuzz
Published
2020-12-05 00:00
Modified
2022-04-13 03:23
Summary
Heap-buffer-overflow in flb_http_do
Details

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28256

Crash type: Heap-buffer-overflow WRITE 1
Crash state:
flb_http_do
http_fuzzer.c
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "severity": "HIGH"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "fluent-bit"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "10ceb5b2ab6635a000f3eceaa267e1e34496de6b"
            },
            {
              "fixed": "16f4084f36c78d1c121a78aafb7dc1db5fe699e9"
            },
            {
              "fixed": "b4036d78e0963f9051bea9501437852d0bf6772e"
            },
            {
              "fixed": "d5e58829f7aa930d4d2dafbe8cd9fdfb080be924"
            }
          ],
          "repo": "https://github.com/fluent/fluent-bit/",
          "type": "GIT"
        }
      ],
      "versions": [
        "v1.7.0",
        "v1.7.0-rc1",
        "v1.7.0-rc2",
        "v1.7.0-rc3",
        "v1.7.0-rc4",
        "v1.7.0-rc5",
        "v1.7.0-rc6",
        "v1.7.0-rc7",
        "v1.7.0-rc8",
        "v1.7.0-rc9",
        "v1.7.1"
      ]
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28256\n\n```\nCrash type: Heap-buffer-overflow WRITE 1\nCrash state:\nflb_http_do\nhttp_fuzzer.c\n```\n",
  "id": "OSV-2020-2239",
  "modified": "2022-04-13T03:23:34.051218Z",
  "published": "2020-12-05T00:00:32.824865Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28256"
    }
  ],
  "summary": "Heap-buffer-overflow in flb_http_do"
}


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.