rustsec-2026-0115
Vulnerability from osv_rustsec
Published
2026-05-01 12:00
Modified
2026-05-07 08:56
Summary
Fragile bounds check when sampling from image
Details

A read of pixels was coded as modifying coordinates to lie within the image bounds. It would calculate a coordinate by adding a constant to an input and taking the minimum of the resulting coordinate and 'dimension - 1'. This would not protect against malicious inputs that could overflow the addition. . Subsequently to the tricked bounds check the image could then be sampled at multiple, differently calculated coordinates exceeding the bounds.

References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "categories": [
          "memory-exposure"
        ],
        "cvss": null,
        "informational": "unsound"
      },
      "ecosystem_specific": {
        "affected_functions": null,
        "affects": {
          "arch": [],
          "functions": [
            "imageproc::binary_descriptors::brief"
          ],
          "os": []
        }
      },
      "package": {
        "ecosystem": "crates.io",
        "name": "imageproc",
        "purl": "pkg:cargo/imageproc"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.24.0"
            },
            {
              "fixed": "0.24.1"
            },
            {
              "introduced": "0.25.0"
            },
            {
              "fixed": "0.25.1"
            },
            {
              "introduced": "0.26.0"
            },
            {
              "fixed": "0.26.2"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": []
    }
  ],
  "aliases": [
    "GHSA-5qv7-j6w5-fr4m"
  ],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "A read of pixels was coded as modifying coordinates to lie within the image\nbounds. It would calculate a coordinate by adding a constant to an input and\ntaking the minimum of the resulting coordinate and \u0027dimension - 1\u0027. This would\nnot protect against malicious inputs that could overflow the addition. .\nSubsequently to the tricked bounds check the image could then be sampled at\nmultiple, differently calculated coordinates exceeding the bounds.",
  "id": "RUSTSEC-2026-0115",
  "modified": "2026-05-07T08:56:41Z",
  "published": "2026-05-01T12:00:00Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://crates.io/crates/imageproc"
    },
    {
      "type": "ADVISORY",
      "url": "https://rustsec.org/advisories/RUSTSEC-2026-0115.html"
    }
  ],
  "related": [
    "https://github.com/image-rs/imageproc/pull/778"
  ],
  "severity": [],
  "summary": "Fragile bounds check when sampling from image"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.



Detection rules are retrieved from Rulezet.