CVE-2017-5848: Buffer Overflow

Published Feb 6, 2017
·
Updated

Invalid memory read and possible buffer overflows were found in PSM parser.

Upstream bug:

https://bugzilla.gnome.org/showbug.cgi?id=777957

Upstream patch:

https://github.com/GStreamer/gst-plugins-bad/commit/948b87bf1514de

CVE assignment:

http://seclists.org/oss-sec/2017/q1/284

Other sources

The gstpsdemuxparsepsm function in gst/mpegdemux/gstmpegdemux.c in gst-plugins-bad in GStreamer allows remote attackers to cause a denial of service (invalid memory read and crash) via vectors involving PSM parsing.

Affected Software

16 affected components
Gstreamer Project Gstreamer<1.11.2
Debian Debian Linux=8.0
Debian Debian Linux=9.0
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Eus=7.4
redhat Enterprise Linux Eus=7.5
redhat Enterprise Linux Eus=7.6
redhat Enterprise Linux Eus=7.7
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=7.4
redhat Enterprise Linux Server Aus=7.6
redhat Enterprise Linux Server Aus=7.7
redhat Enterprise Linux Server Tus=7.6
redhat Enterprise Linux Server Tus=7.7
redhat Enterprise Linux Workstation=7.0
GStreamer GStreamer<1.11.2

Event History

Feb 6, 2017
Data Sourced
via Red Hat·02:59 PM
DescriptionSeverityAffected Software
Feb 9, 2017
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Data Sourced
via NVD·03:59 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2017-5848?

The severity of CVE-2017-5848 is classified as high due to potential buffer overflows and invalid memory access.

2

How do I fix CVE-2017-5848?

To fix CVE-2017-5848, you should update GStreamer to version 1.11.3 or later where the vulnerability has been patched.

3

Which software versions are affected by CVE-2017-5848?

CVE-2017-5848 affects GStreamer versions prior to 1.11.3, Debian 8.0 and 9.0, and Red Hat Enterprise Linux versions 7.0, 7.4, 7.5, 7.6, and 7.7.

4

What are the risks associated with CVE-2017-5848?

The risks associated with CVE-2017-5848 include possible exploitation that may lead to remote code execution or application crashes.

5

Is CVE-2017-5848 being actively exploited in the wild?

As of now, there are no specific reports confirming active exploitation of CVE-2017-5848 in the wild.

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