VDB-262546 · CVE-2024-34149 · GCVE-0-2024-34149

Bitcoin Core/Knots tapscript privilege escalation ⚔ [Disputed]

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

Summaryinfo

A vulnerability was found in Bitcoin Core and Knots and classified as problematic. This impacts an unknown function of the component tapscript. Executing a manipulation can lead to an unknown weakness. This vulnerability is handled as CVE-2024-34149. There is not any exploit available. There are still doubts about whether this vulnerability truly exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Bitcoin Core and Knots (the affected version is unknown). It has been declared as problematic. This vulnerability affects an unknown code of the component tapscript. The impact remains unknown. CVE summarizes:

In Bitcoin Core through 27.0 and Bitcoin Knots before 25.1.knots20231115, tapscript lacks a policy size limit check, a different issue than CVE-2023-50428. NOTE: some parties oppose this new limit check (for example, because they agree with the objective but disagree with the technical mechanism, or because they have a different objective).

The advisory is available at github.com. This vulnerability was named CVE-2024-34149. The technical details are unknown and an exploit is not available.

The real existence of this vulnerability is still doubted at the moment.

Upgrading eliminates this vulnerability.

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

Productinfo

Vendor

Bitcoin

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

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: Privilege escalation
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
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: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

04/30/2024 🔍
05/01/2024 +0 days 🔍
07/30/2024 +90 days 🔍

Sourcesinfo

Advisory: github.com
Status: Confirmed
Disputed: 🔍

CVE: CVE-2024-34149 (🔍)
GCVE (CVE): GCVE-0-2024-34149
GCVE (VulDB): GCVE-100-262546

Entryinfo

Created: 05/01/2024 01:17
Updated: 07/30/2024 18:29
Changes: 05/01/2024 01:17 (50), 07/30/2024 18:29 (1)
Complete: 🔍
Cache ID: 216::103