rustsec-2025-0169
Vulnerability from osv_rustsec
Published
2025-04-24 12:00
Modified
2026-08-11 10:24
Summary
`FormatContext` stream accessors can cause undefined behavior from safe code
Details

Affected versions of stainless_ffmpeg exposed several safe public methods on FormatContext that accepted a stream_index parameter and used it in unsafe pointer operations without checking whether the index was valid. These methods performed pointer arithmetic and dereferenced the resulting stream pointer. Safe callers could pass a negative or out-of-bounds stream_index, which could cause out-of-bounds pointer access and undefined behavior from safe Rust code.

The issue was fixed in version 0.6.0 by marking the affected stream accessor methods as unsafe and documenting that callers must ensure stream_index is a valid stream index.

References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "categories": [],
        "cvss": null,
        "informational": "unsound"
      },
      "ecosystem_specific": {
        "affected_functions": null,
        "affects": {
          "arch": [],
          "functions": [
            "stainless_ffmpeg::format_context::FormatContext::get_codec_id",
            "stainless_ffmpeg::format_context::FormatContext::get_stream",
            "stainless_ffmpeg::format_context::FormatContext::get_stream_type",
            "stainless_ffmpeg::format_context::FormatContext::get_stream_type_name"
          ],
          "os": []
        }
      },
      "package": {
        "ecosystem": "crates.io",
        "name": "stainless_ffmpeg",
        "purl": "pkg:cargo/stainless_ffmpeg"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.0-0"
            },
            {
              "fixed": "0.6.0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": []
    }
  ],
  "aliases": [],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "Affected versions of `stainless_ffmpeg` exposed several safe public methods on `FormatContext` that accepted a `stream_index` parameter and used it in unsafe pointer operations without checking whether the index was valid. These methods performed pointer arithmetic and dereferenced the resulting stream pointer. Safe callers could pass a negative or out-of-bounds `stream_index`, which could cause out-of-bounds pointer access and undefined behavior from safe Rust code.\n\nThe issue was fixed in version `0.6.0` by marking the affected stream accessor methods as `unsafe` and documenting that callers must ensure `stream_index` is a valid stream index.",
  "id": "RUSTSEC-2025-0169",
  "modified": "2026-08-11T10:24:59Z",
  "published": "2025-04-24T12:00:00Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://crates.io/crates/stainless_ffmpeg"
    },
    {
      "type": "ADVISORY",
      "url": "https://rustsec.org/advisories/RUSTSEC-2025-0169.html"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/nomalab/stainless-ffmpeg/issues/63"
    },
    {
      "type": "WEB",
      "url": "https://github.com/nomalab/stainless-ffmpeg/pull/64"
    },
    {
      "type": "WEB",
      "url": "https://github.com/nomalab/stainless-ffmpeg/commit/a649e8cb4e7c9859279d1dc85051df5e7a4932f7"
    }
  ],
  "related": [],
  "severity": [],
  "summary": "`FormatContext` stream accessors can cause undefined behavior from safe code"
}



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.