danswer-ai danswer up to 0.3.94 resource consumption

Summaryinfo

A vulnerability was found in danswer-ai danswer up to 0.3.94 and classified as problematic. Affected by this issue is some unknown functionality. Such manipulation leads to resource consumption. This vulnerability is referenced as CVE-2024-8028. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability was found in danswer-ai danswer up to 0.3.94 and classified as problematic. Affected by this issue is an unknown code. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability. CVE summarizes:

A vulnerability in danswer-ai/danswer v0.3.94 allows an attacker to cause a Denial of Service (DoS) by uploading a file with a malformed multipart boundary. By appending a large number of characters to the end of the multipart boundary, the server continuously processes each character, rendering the application inaccessible. This issue can be exploited by sending a single crafted request, affecting all users on the server.

The advisory is available at huntr.com. This vulnerability is handled as CVE-2024-8028 since 08/20/2024. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.

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

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

Productinfo

Type

• Artificial Intelligence Software

Vendor

• danswer-ai

Name

• danswer

Version

• 0.3.0
• 0.3.1
• 0.3.2
• 0.3.3
• 0.3.4
• 0.3.5
• 0.3.6
• 0.3.7
• 0.3.8
• 0.3.9
• 0.3.10
• 0.3.11
• 0.3.12
• 0.3.13
• 0.3.14
• 0.3.15
• 0.3.16
• 0.3.17
• 0.3.18
• 0.3.19
• 0.3.20
• 0.3.21
• 0.3.22
• 0.3.23
• 0.3.24
• 0.3.25
• 0.3.26
• 0.3.27
• 0.3.28
• 0.3.29
• 0.3.30
• 0.3.31
• 0.3.32
• 0.3.33
• 0.3.34
• 0.3.35
• 0.3.36
• 0.3.37
• 0.3.38
• 0.3.39
• 0.3.40
• 0.3.41
• 0.3.42
• 0.3.43
• 0.3.44
• 0.3.45
• 0.3.46
• 0.3.47
• 0.3.48
• 0.3.49
• 0.3.50
• 0.3.51
• 0.3.52
• 0.3.53
• 0.3.54
• 0.3.55
• 0.3.56
• 0.3.57
• 0.3.58
• 0.3.59
• 0.3.60
• 0.3.61
• 0.3.62
• 0.3.63
• 0.3.64
• 0.3.65
• 0.3.66
• 0.3.67
• 0.3.68
• 0.3.69
• 0.3.70
• 0.3.71
• 0.3.72
• 0.3.73
• 0.3.74
• 0.3.75
• 0.3.76
• 0.3.77
• 0.3.78
• 0.3.79
• 0.3.80
• 0.3.81
• 0.3.82
• 0.3.83
• 0.3.84
• 0.3.85
• 0.3.86
• 0.3.87
• 0.3.88
• 0.3.89
• 0.3.90
• 0.3.91
• 0.3.92
• 0.3.93
• 0.3.94

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

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

Discussion