ireader media-server librtmp use after free

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.
5.4$0-$5k0.00

Summaryinfo

A vulnerability described as problematic has been identified in ireader media-server. This issue affects some unknown processing of the component librtmp. Executing a manipulation can lead to use after free. This vulnerability is registered as CVE-2022-40016. No exploit is available. A patch should be applied to remediate this issue.

Detailsinfo

A vulnerability has been found in ireader media-server (unknown version) and classified as problematic. This vulnerability affects an unknown code block of the component librtmp. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect availability. CVE summarizes:

Use After Free (UAF) vulnerability in ireader media-server before commit 3e0f63f1d3553f75c7d4eb32fa7c7a1976a9ff84 in librtmp, allows attackers to cause a denial of service.

The weakness was published 02/16/2023 as 235. The advisory is available at github.com. This vulnerability was named CVE-2022-40016 since 09/06/2022. The technical details are unknown and an exploit is not available.

Applying the patch 3e0f63f1d3553f75c7d4eb32fa7c7a1976a9ff84 is able to eliminate this problem.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-43341). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

Name

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

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

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: 3e0f63f1d3553f75c7d4eb32fa7c7a1976a9ff84

Timelineinfo

09/06/2022 🔍
02/16/2023 +163 days 🔍
02/16/2023 +0 days 🔍
07/24/2026 +1254 days 🔍

Sourcesinfo

Product: github.com

Advisory: 235
Status: Confirmed

CVE: CVE-2022-40016 (🔍)
GCVE (CVE): GCVE-0-2022-40016
GCVE (VulDB): GCVE-100-221170
EUVD: 🔍

Entryinfo

Created: 02/16/2023 08:24
Updated: 07/24/2026 03:41
Changes: 02/16/2023 08:24 (40), 03/16/2023 12:39 (11), 07/24/2026 03:41 (16)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!