LIEF 365a16a BinaryStream.hpp assertion

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.5	$0-$5k	0.00

Summaryinfo

A vulnerability was found in LIEF 365a16a. It has been rated as problematic. The impacted element is an unknown function of the file BinaryStream.hpp. The manipulation leads to assertion. This vulnerability is listed as CVE-2022-38496. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in LIEF 365a16a. This issue affects an unknown function of the file BinaryStream.hpp. The manipulation with an unknown input leads to a assertion vulnerability. Using CWE to declare the problem leads to CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. Impacted is availability. The summary by CVE is:

LIEF commit 365a16a was discovered to contain a reachable assertion abort via the component BinaryStream.hpp.

The weakness was presented 09/14/2022 as 765. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2022-38496 since 08/22/2022. Technical details of the vulnerability are known, but there is no available exploit.

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

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

Productinfo

Name

LIEF

Version

365a16a

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.5
VulDB Meta Temp Score: 4.5

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

NVD Base Score: 5.5
NVD 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: Assertion
CWE: CWE-617
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

08/22/2022 🔍
09/14/2022 +23 days 🔍
09/14/2022 +0 days 🔍
10/17/2022 +33 days 🔍

Sourcesinfo

Advisory: 765
Status: Confirmed

CVE: CVE-2022-38496 (🔍)
GCVE (CVE): GCVE-0-2022-38496
GCVE (VulDB): GCVE-100-208523

Entryinfo

Created: 09/14/2022 10:30
Updated: 10/17/2022 08:10
Changes: 09/14/2022 10:30 (37), 10/17/2022 08:10 (11)
Complete: 🔍
Cache ID: 216::103