rustsec-2026-0116
Vulnerability from osv_rustsec
Published
2026-05-01 12:00
Modified
2026-05-07 08:56
Summary
Improper check of an invariant resulting in incorrect bounds checks
Details

A bounds verification of a slice storage of a 2-dimensional matrix's coefficients (a kernel) would compare the total size against the product of individual dimensions. This would erroneously cast after the multiplication and consequently fail to detect possible violations when overflow occurs.

Afterwards, the individual sizes were trusted to properly constrain coordinates within the matrix to indices valid for the underlying storage. With a crafted Kernel object, certain combinations of coordinates could then cause an out-of-bounds access in an unsafe function while fulfilling its documented preconditions. The kernel value could be passed to library functions that trusted the preconditions and then performed such reads.

References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "categories": [
          "memory-exposure"
        ],
        "cvss": null,
        "informational": "unsound"
      },
      "ecosystem_specific": {
        "affected_functions": null,
        "affects": {
          "arch": [],
          "functions": [],
          "os": []
        }
      },
      "package": {
        "ecosystem": "crates.io",
        "name": "imageproc",
        "purl": "pkg:cargo/imageproc"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.0-0"
            },
            {
              "fixed": "0.23.1"
            },
            {
              "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-w5p8-4jcx-2j6r"
  ],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "A bounds verification of a slice storage of a 2-dimensional matrix\u0027s\ncoefficients (a kernel) would compare the total size against the product of\nindividual dimensions. This would erroneously cast *after* the multiplication\nand consequently fail to detect possible violations when overflow occurs.\n\nAfterwards, the individual sizes were trusted to properly constrain coordinates\nwithin the matrix to indices valid for the underlying storage. With a crafted\n`Kernel` object, certain combinations of coordinates could then cause an\nout-of-bounds access in an `unsafe` function while fulfilling its documented\npreconditions. The kernel value could be passed to library functions that\ntrusted the preconditions and then performed such reads.",
  "id": "RUSTSEC-2026-0116",
  "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-0116.html"
    }
  ],
  "related": [
    "https://github.com/image-rs/imageproc/pull/777"
  ],
  "severity": [],
  "summary": "Improper check of an invariant resulting in incorrect bounds checks"
}


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.