Bento4 1.5.0-616 SDK Core/Ap4StscAtom.h MP4 File memory corruption
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Bento4 1.5.0-616. Affected is an unknown function of the file Core/Ap4StscAtom.h of the component SDK. The manipulation as part of MP4 File leads to memory corruption. This vulnerability is traded as CVE-2017-14258. It is possible to launch the attack on the local host. There is no exploit available. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in Bento4 1.5.0-616 (Multimedia Player Software). It has been rated as critical. This issue affects some unknown processing of the file Core/Ap4StscAtom.h of the component SDK. The manipulation as part of a MP4 File leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In the SDK in Bento4 1.5.0-616, SetItemCount in Core/Ap4StscAtom.h file contains a Write Memory Access Violation vulnerability. It is possible to exploit this vulnerability and possibly execute arbitrary code by opening a crafted .MP4 file.
The bug was discovered 09/10/2017. The weakness was presented 09/11/2017 (GitHub Repository). It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2017-14258 since 09/10/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-106342, VDB-106344, VDB-106345 and VDB-106346 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 4.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/10/2017 🔍09/10/2017 🔍
09/11/2017 🔍
09/11/2017 🔍
09/11/2017 🔍
12/28/2022 🔍
Sources
Advisory: 181Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-14258 (🔍)
GCVE (CVE): GCVE-0-2017-14258
GCVE (VulDB): GCVE-100-106343
See also: 🔍
Entry
Created: 09/11/2017 16:18Updated: 12/28/2022 10:18
Changes: 09/11/2017 16:18 (53), 11/14/2019 15:20 (8), 12/28/2022 10:18 (4)
Complete: 🔍
Cache ID: 216:CBE:103
No comments yet. Languages: en.
Please log in to comment.