parisneo lollms-webui up to 0.2.61 Model Files equivalent special elements

Summaryinfo

A vulnerability identified as problematic has been detected in parisneo lollms-webui up to 0.2.61. Affected by this vulnerability is an unknown functionality of the component Model Files Handler. Performing a manipulation results in improper neutralization of equivalent special elements. This vulnerability is reported as CVE-2024-4897. The attack requires a local approach. No exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, was found in parisneo lollms-webui up to 0.2.61. This affects some unknown functionality of the component Model Files Handler. The manipulation with an unknown input leads to a improper neutralization of equivalent special elements vulnerability. CWE is classifying the issue as CWE-76. The product correctly neutralizes certain special elements, but it improperly neutralizes equivalent special elements. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

parisneo/lollms-webui, in its latest version, is vulnerable to remote code execution due to an insecure dependency on llama-cpp-python version llama_cpp_python-0.2.61+cpuavx2-cp311-cp311-manylinux_2_31_x86_64. The vulnerability arises from the application's 'binding_zoo' feature, which allows attackers to upload and interact with a malicious model file hosted on hugging-face, leading to remote code execution. The issue is linked to a known vulnerability in llama-cpp-python, CVE-2024-34359, which has not been patched in lollms-webui as of commit b454f40a. The vulnerability is exploitable through the application's handling of model files in the 'bindings_zoo' feature, specifically when processing gguf format model files.

The advisory is shared at huntr.com. This vulnerability is uniquely identified as CVE-2024-4897 since 05/15/2024. The exploitability is told to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.

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 the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• parisneo

Name

• lollms-webui

Version

• 0.2.0
• 0.2.1
• 0.2.2
• 0.2.3
• 0.2.4
• 0.2.5
• 0.2.6
• 0.2.7
• 0.2.8
• 0.2.9
• 0.2.10
• 0.2.11
• 0.2.12
• 0.2.13
• 0.2.14
• 0.2.15
• 0.2.16
• 0.2.17
• 0.2.18
• 0.2.19
• 0.2.20
• 0.2.21
• 0.2.22
• 0.2.23
• 0.2.24
• 0.2.25
• 0.2.26
• 0.2.27
• 0.2.28
• 0.2.29
• 0.2.30
• 0.2.31
• 0.2.32
• 0.2.33
• 0.2.34
• 0.2.35
• 0.2.36
• 0.2.37
• 0.2.38
• 0.2.39
• 0.2.40
• 0.2.41
• 0.2.42
• 0.2.43
• 0.2.44
• 0.2.45
• 0.2.46
• 0.2.47
• 0.2.48
• 0.2.49
• 0.2.50
• 0.2.51
• 0.2.52
• 0.2.53
• 0.2.54
• 0.2.55
• 0.2.56
• 0.2.57
• 0.2.58
• 0.2.59
• 0.2.60
• 0.2.61

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion