REDHAT-BUG-2491321: Medium severity GStreamer gst-plugins-bad vulnerability

Published Jun 22, 2026
·
Updated

A 1-byte heap out-of-bounds read vulnerability exists in the gsth264parseprocessnal() function in subprojects/gst-plugins-bad/gst/videoparsers/gsth264parse.c. The function processes H.264 NAL units including GSTH264NALSLICEEXT (NAL type 20) for MVC/SVC extension slices. At line 1132, the code dereferences (nalu->data + nalu->offset + nalu->headerbytes) to check the firstmbinslice flag without first verifying that nalu->size > nalu->headerbytes. For extension slice types, headerbytes is set to 4 (1 byte base + 3 bytes extension header per gsth264parser.c:243). A malformed NAL unit with exactly size==4 passes the minimum size check (size >= 2 at line 999) but triggers a 1-byte read at offset 4, which is beyond the allocated buffer. The same bounds check pattern is correctly implemented in gsth264parsecollectnal() at line 1259 with if (nalu->size > nalu->headerbytes). The vulnerability affects GStreamer 1.x versions (tested against git version 1.29.1.1). Upstream maintainer Sebastian Droege confirmed the vulnerability via GitLab work item 5108. Reported by Dr. Faruk Kazi, Ramesh Adhikari, and Ariba Afroz from CoE-CNDS Lab, VJTI, Mumbai, India. PSIRT Ticket: PSIRTSUPT-17585.

Affected Software

1 affected component
GStreamer gst-plugins-bad>=1.0.0<=1.29.1.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Before dereferencing *(nalu->data + nalu->offset + nalu->header_bytes) (around line 1132) add a check that nalu->size > nalu->header_bytes (e.g. if (nalu->size > nalu->header_bytes) { /* existing access */ }). Mirror the bounds check used in gst_h264_parse_collect_nal() at line 1259 to ensure the first_mb_in_slice access cannot read past the NAL unit buffer.

    gst-plugins-bad/gst/videoparsers/gsth264parse.c :: gst_h264_parse_process_nal() nalu->size > nalu->header_bytes bounds check = add/enable

Event History

Jun 22, 2026
Data Sourced
via Red Hat·11:33 AM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-2491321?

The severity of REDHAT-BUG-2491321 is medium, rated as 4.

2

How do I fix REDHAT-BUG-2491321?

To fix REDHAT-BUG-2491321, update your GStreamer gst-plugins-bad package to the latest version that addresses the vulnerability.

3

What does REDHAT-BUG-2491321 affect?

REDHAT-BUG-2491321 affects the gst_h264_parse_process_nal() function found in the GStreamer gst-plugins-bad package.

4

What is the nature of the vulnerability in REDHAT-BUG-2491321?

The nature of the vulnerability in REDHAT-BUG-2491321 is a 1-byte heap out-of-bounds read.

5

When was REDHAT-BUG-2491321 published?

REDHAT-BUG-2491321 was published on June 22, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203