Bitmessage PyBitmessage up to 0.6.3.2 apinotifypath state issue ⚔ [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.6$0-$5k0.00

Summaryinfo

A vulnerability described as critical has been identified in Bitmessage PyBitmessage up to 0.6.3.2. The impacted element is an unknown function. The manipulation of the argument apinotifypath results in state issue. This vulnerability is known as CVE-2021-26917. It is possible to launch the attack remotely. Furthermore, an exploit is available. There is ongoing doubt regarding the real existence of this vulnerability.

Detailsinfo

A vulnerability was found in Bitmessage PyBitmessage up to 0.6.3.2. It has been classified as critical. Affected is an unknown code block. The manipulation of the argument apinotifypath with an unknown input leads to a state issue vulnerability. CWE is classifying the issue as CWE-371. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was published 02/09/2021. The advisory is shared for download at poal.co. This vulnerability is traded as CVE-2021-26917. Technical details and a public exploit are known.

The exploit is shared for download at poal.co. It is declared as proof-of-concept. The real existence of this vulnerability is still doubted at the moment.

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

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.9
VulDB Meta Temp Score: 5.8

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: State issue
CWE: CWE-371
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

02/08/2021 🔍
02/09/2021 +1 days 🔍
02/09/2021 +0 days 🔍
08/03/2024 +1271 days 🔍

Sourcesinfo

Advisory: poal.co
Status: Not defined
Disputed: 🔍

CVE: CVE-2021-26917 (🔍)
GCVE (CVE): GCVE-0-2021-26917
GCVE (VulDB): GCVE-100-169440
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 02/09/2021 09:43
Updated: 08/03/2024 23:27
Changes: 02/09/2021 09:43 (40), 02/25/2021 21:14 (2), 02/25/2021 21:18 (18), 08/03/2024 23:27 (17)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

 Bitmessage (+0)
5 years ago
There is no vulnerability. In the very worst case, it's a bug, and I'm not even sure about that at the moment. It looks like the user-provided script is interpreted through shell rather than through python as the user wanted. All the code to be executed, malicious or not, needs to be provided by the user. It can't be installed remotely and there is no privilege escalation. All it does is what the user tells it to do.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!