Ubuntu patches GStreamer RTSP and video-handling flaws
A remote attacker may crash GStreamer via RTSP, and a local attacker may run code.
Heap buffer overflow in GStreamer gst-plugins-base
A heap buffer overflow in GStreamer's gst-plugins-base occurs when a video buffer's attached GstVideoMeta declares plane strides and offsets larger than the actual backing allocation. The metadata is not range-checked on deserialization, and frame-mapping code does not confirm that the declared plane geometry fits in the buffer before consumers read or write it. A local attacker who controls the sending side of a GStreamer inter-process pipeline can supply a crafted buffer and cause the receiving process to access memory past the heap allocation, leading to denial of service or possible code execution in that process. The issue affects deployments of gst-plugins-base; the advisory data does not name a version range. It is not listed in CISA KEV, and no public proof-of-concept is known.
What to do: Install the gst-plugins-base update from your distribution or GStreamer vendor as soon as a fixed package is published, and restart processes that link against it. Until then, do not let untrusted local processes act as the sending side of GStreamer inter-process pipelines that carry video buffers with GstVideoMeta. Treat any crash in a media process that maps IPC video frames as a possible indicator and isolate that pipeline.
| Product | Affected |
|---|---|
| GStreamer gst-plugins-base | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
A flaw was found in gst-plugins-base. A heap buffer overflow can be triggered when processing video buffers whose attached GstVideoMeta metadata declares plane strides and offsets that exceed the actual backing memory allocation. The metadata is not range-checked during deserialization, and the video frame mapping code does not verify that the declared plane geometry fits within the buffer before allowing consumers to read or write video data. A local attacker who controls the sending side of a GStreamer inter-process IPC pipeline can deliver a crafted buffer carrying fabricated strides, causing the receiving process to read or write beyond heap boundaries. Successful exploitation can cause a denial of service or potentially allow code execution within the affected process.
A remote attacker may crash GStreamer via RTSP, and a local attacker may run code.
Today 1K readers · 1.1K views · 101 reads · all time 211K views