Brave Browser up to 1.43.87 ipfs Scheme denial of service

Summaryinfo

A vulnerability was found in Brave Browser up to 1.43.87. It has been classified as problematic. This impacts an unknown function of the component ipfs Scheme Handler. Performing a manipulation results in denial of service. This vulnerability was named CVE-2022-47934. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Brave Browser up to 1.43.87. It has been classified as problematic. This affects an unknown code block of the component ipfs Scheme Handler. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:

Brave Browser before 1.43.88 allowed a remote attacker to cause a denial of service in private and guest windows via a crafted HTML file that mentions an ipfs:// or ipns:// URL. This is caused by an incomplete fix for CVE-2022-47932 and CVE-2022-47934.

The weakness was presented 12/25/2022 as 24211. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-47934 since 12/23/2022. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 1.43.88 eliminates this vulnerability. Applying the patch 82d8e39043e691e0492519126437275511ee87e8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Brave

Name

• Browser

Version

• 1.43.0
• 1.43.1
• 1.43.2
• 1.43.3
• 1.43.4
• 1.43.5
• 1.43.6
• 1.43.7
• 1.43.8
• 1.43.9
• 1.43.10
• 1.43.11
• 1.43.12
• 1.43.13
• 1.43.14
• 1.43.15
• 1.43.16
• 1.43.17
• 1.43.18
• 1.43.19
• 1.43.20
• 1.43.21
• 1.43.22
• 1.43.23
• 1.43.24
• 1.43.25
• 1.43.26
• 1.43.27
• 1.43.28
• 1.43.29
• 1.43.30
• 1.43.31
• 1.43.32
• 1.43.33
• 1.43.34
• 1.43.35
• 1.43.36
• 1.43.37
• 1.43.38
• 1.43.39
• 1.43.40
• 1.43.41
• 1.43.42
• 1.43.43
• 1.43.44
• 1.43.45
• 1.43.46
• 1.43.47
• 1.43.48
• 1.43.49
• 1.43.50
• 1.43.51
• 1.43.52
• 1.43.53
• 1.43.54
• 1.43.55
• 1.43.56
• 1.43.57
• 1.43.58
• 1.43.59
• 1.43.60
• 1.43.61
• 1.43.62
• 1.43.63
• 1.43.64
• 1.43.65
• 1.43.66
• 1.43.67
• 1.43.68
• 1.43.69
• 1.43.70
• 1.43.71
• 1.43.72
• 1.43.73
• 1.43.74
• 1.43.75
• 1.43.76
• 1.43.77
• 1.43.78
• 1.43.79
• 1.43.80
• 1.43.81
• 1.43.82
• 1.43.83
• 1.43.84
• 1.43.85
• 1.43.86
• 1.43.87

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion