tsMuxer git-2539d07 MP4 File memory leak

HistoryDiffrelatejsonxmlCTI

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.8	$0-$5k	0.00

Summaryinfo

A vulnerability has been found in tsMuxer git-2539d07 and classified as problematic. This vulnerability affects unknown code of the component MP4 File Handler. Performing a manipulation results in memory leak. This vulnerability is identified as CVE-2023-45511. There is not any exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in tsMuxer git-2539d07. This affects an unknown part of the component MP4 File Handler. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on availability. The summary by CVE is:

A memory leak in tsMuxer version git-2539d07 allows attackers to cause a Denial of Service (DoS) via a crafted MP4 file.

The weakness was released 10/13/2023 as 780. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2023-45511 since 10/09/2023. The technical details are unknown and an exploit is not publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-49803). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

tsMuxer

Version

git-2539d07

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.8

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CNA Base Score: 5.5
CNA Vector: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

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 Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

10/09/2023 🔍
10/13/2023 +4 days 🔍
10/13/2023 +0 days 🔍
02/10/2026 +851 days 🔍

Sourcesinfo

Advisory: 780
Status: Not defined

CVE: CVE-2023-45511 (🔍)
GCVE (CVE): GCVE-0-2023-45511
GCVE (VulDB): GCVE-100-242091
EUVD: 🔍

Entryinfo

Created: 10/13/2023 08:49
Updated: 02/10/2026 15:07
Changes: 10/13/2023 08:49 (38), 11/02/2023 06:51 (11), 09/19/2024 04:56 (27), 02/10/2026 15:07 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.