osv-2021-1577
Vulnerability from osv_ossfuzz
Published
2021-11-14 00:01
Modified
2022-04-13 03:04
Summary
Heap-buffer-overflow in apreq_header_attribute
Details

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

Crash type: Heap-buffer-overflow READ 1
Crash state:
apreq_header_attribute
create_multipart_context
apreq_parse_multipart

{
  "affected": [
    {
      "ecosystem_specific": {
        "severity": "MEDIUM"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "apache-httpd"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "beec41a39a7206a8ed95d6aac31631a2f10118cd"
            },
            {
              "fixed": "6b1247e8a6ce5708d57187cb33db5f6da96f86dc"
            }
          ],
          "repo": "https://github.com/apache/httpd",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40985\n\n```\nCrash type: Heap-buffer-overflow READ 1\nCrash state:\napreq_header_attribute\ncreate_multipart_context\napreq_parse_multipart\n```\n",
  "id": "OSV-2021-1577",
  "modified": "2022-04-13T03:04:35.778838Z",
  "published": "2021-11-14T00:01:26.531147Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40985"
    }
  ],
  "summary": "Heap-buffer-overflow in apreq_header_attribute"
}


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…