osv-2026-610
Vulnerability from osv_ossfuzz
Published
2026-04-22 00:07
Modified
2026-05-01 14:26
Summary
Memcpy-param-overlap in htx_replace_blk_value
Details

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

Crash type: Memcpy-param-overlap
Crash state:
htx_replace_blk_value
http_replace_header_value
http_scheme_based_normalize

{
  "affected": [
    {
      "database_specific": {
        "fixed_range": "213ee17119774aeaf6ee153117fb522e9d8d7d99:76d894956f7c83bd503afc65a8c8240a6c527f40"
      },
      "ecosystem_specific": {
        "severity": "MEDIUM"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "haproxy",
        "purl": "pkg:generic/haproxy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "41bded895292573a8fbe9817499c5e996fb5e4ea"
            },
            {
              "fixed": "76d894956f7c83bd503afc65a8c8240a6c527f40"
            }
          ],
          "repo": "https://github.com/haproxy/haproxy",
          "type": "GIT"
        }
      ],
      "versions": [
        "v3.4-dev10",
        "v3.4-dev9"
      ]
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=504612570\n\n```\nCrash type: Memcpy-param-overlap\nCrash state:\nhtx_replace_blk_value\nhttp_replace_header_value\nhttp_scheme_based_normalize\n```\n",
  "id": "OSV-2026-610",
  "modified": "2026-05-01T14:26:40.032545Z",
  "published": "2026-04-22T00:07:53.902461Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=504612570"
    }
  ],
  "schema_version": "1.7.5",
  "summary": "Memcpy-param-overlap in htx_replace_blk_value"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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…