parisneo lollms lollms_binding_infos check_access client_id critical step in authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in parisneo lollms. The impacted element is the function check_access of the component lollms_binding_infos. Performing a manipulation of the argument client_id results in critical step in authentication.
This vulnerability is identified as CVE-2024-11302. The attack is only possible with local access. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, was found in parisneo lollms (affected version not known). This affects the function check_access of the component lollms_binding_infos. The manipulation of the argument client_id with an unknown input leads to a critical step in authentication vulnerability. CWE is classifying the issue as CWE-304. The product implements an authentication technique, but it skips a step that weakens the technique. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A missing check_access() function in the lollms_binding_infos module of the parisneo/lollms repository, version V14, allows attackers to add, modify, and remove bindings arbitrarily. This vulnerability affects the /install_binding and /reinstall_binding endpoints, among others, enabling unauthorized access and manipulation of binding settings without requiring the client_id value.
It is possible to read the advisory at huntr.com. This vulnerability is uniquely identified as CVE-2024-11302 since 11/16/2024. The exploitability is told to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.6
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.0
CNA Vector (@huntr_ai): 🔍
CVSSv2
| 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: 🔍
Exploiting
Class: Critical step in authenticationCWE: CWE-304
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/16/2024 🔍03/20/2025 🔍
03/20/2025 🔍
03/20/2025 🔍
Sources
Advisory: huntr.comStatus: Not defined
CVE: CVE-2024-11302 (🔍)
GCVE (CVE): GCVE-0-2024-11302
GCVE (VulDB): GCVE-100-300351
Entry
Created: 03/20/2025 14:42Changes: 03/20/2025 14:42 (62)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.