Vulnerabilities
Misconfiguration
Runtime Security
Compliance
CVE Vulnerabilities

CVE-2016-9447

Out-of-bounds Read

Published: Jan 23, 2017 | Modified: Nov 07, 2023
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
6.8 IMPORTANT
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V3
7.5 IMPORTANT
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2016-9447
CWEhttps://cwe.mitre.org/data/definitions/125.html

The ROM mappings in the NSF decoder in gstreamer 0.10.x allow remote attackers to cause a denial of service (out-of-bounds read or write) and possibly execute arbitrary code via a crafted NSF music file.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Gstreamer Gstreamer_project 0.10.0 (including) 0.10.0 (including)
Gstreamer Gstreamer_project 0.10.1 (including) 0.10.1 (including)
Gstreamer Gstreamer_project 0.10.2 (including) 0.10.2 (including)
Gstreamer Gstreamer_project 0.10.3 (including) 0.10.3 (including)
Gstreamer Gstreamer_project 0.10.4 (including) 0.10.4 (including)
Gstreamer Gstreamer_project 0.10.5 (including) 0.10.5 (including)
Gstreamer Gstreamer_project 0.10.6 (including) 0.10.6 (including)
Gstreamer Gstreamer_project 0.10.7 (including) 0.10.7 (including)
Gstreamer Gstreamer_project 0.10.8 (including) 0.10.8 (including)
Gstreamer Gstreamer_project 0.10.9 (including) 0.10.9 (including)
Gstreamer Gstreamer_project 0.10.10 (including) 0.10.10 (including)
Gstreamer Gstreamer_project 0.10.11 (including) 0.10.11 (including)
Gstreamer Gstreamer_project 0.10.12 (including) 0.10.12 (including)
Gstreamer Gstreamer_project 0.10.13 (including) 0.10.13 (including)
Gstreamer Gstreamer_project 0.10.14 (including) 0.10.14 (including)
Gstreamer Gstreamer_project 0.10.15 (including) 0.10.15 (including)
Gstreamer Gstreamer_project 0.10.16 (including) 0.10.16 (including)
Gstreamer Gstreamer_project 0.10.17 (including) 0.10.17 (including)
Gstreamer Gstreamer_project 0.10.18 (including) 0.10.18 (including)
Gstreamer Gstreamer_project 0.10.19 (including) 0.10.19 (including)
Gstreamer Gstreamer_project 0.10.20 (including) 0.10.20 (including)
Gstreamer Gstreamer_project 0.10.21 (including) 0.10.21 (including)
Gstreamer Gstreamer_project 0.10.22 (including) 0.10.22 (including)
Gstreamer Gstreamer_project 0.10.23 (including) 0.10.23 (including)
Gstreamer Gstreamer_project 0.10.24 (including) 0.10.24 (including)
Gstreamer Gstreamer_project 0.10.25 (including) 0.10.25 (including)
Gstreamer Gstreamer_project 0.10.26 (including) 0.10.26 (including)
Gstreamer Gstreamer_project 0.10.27 (including) 0.10.27 (including)
Gstreamer Gstreamer_project 0.10.28 (including) 0.10.28 (including)
Gstreamer Gstreamer_project 0.10.29 (including) 0.10.29 (including)
Gstreamer Gstreamer_project 0.10.30 (including) 0.10.30 (including)
Gstreamer Gstreamer_project 0.10.31 (including) 0.10.31 (including)
Gstreamer Gstreamer_project 0.10.32 (including) 0.10.32 (including)
Gstreamer Gstreamer_project 0.10.33 (including) 0.10.33 (including)
Gstreamer Gstreamer_project 0.10.34 (including) 0.10.34 (including)
Gstreamer Gstreamer_project 0.10.35 (including) 0.10.35 (including)
Gstreamer Gstreamer_project 0.10.36 (including) 0.10.36 (including)
Red Hat Enterprise Linux 6 RedHat gstreamer-plugins-bad-free-0:0.10.19-5.el6_8 *
Red Hat Enterprise Linux 7 RedHat gstreamer-plugins-bad-free-0:0.10.23-22.el7_3 *
Gst-plugins-bad0.10 Ubuntu precise *
Gst-plugins-bad0.10 Ubuntu trusty *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2024 Aqua Security Software Ltd.   Privacy Policy | Terms of Use