mintplex-labs anything-llm up to 0.x JSON /api/request-token Username values
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in mintplex-labs anything-llm up to 0.x. Affected is an unknown function of the file /api/request-token of the component JSON Handler. The manipulation of the argument Username results in improper handling of values. This vulnerability is cataloged as CVE-2024-3102. The attack may be launched remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability classified as problematic has been found in mintplex-labs anything-llm up to 0.x. Affected is an unknown part of the file /api/request-token of the component JSON Handler. The manipulation of the argument username with an unknown input leads to a improper handling of values vulnerability. CWE is classifying the issue as CWE-229. The product does not properly handle when the expected number of values for parameters, fields, or arguments is not provided in input, or if those values are undefined. This is going to have an impact on confidentiality. CVE summarizes:
A JSON Injection vulnerability exists in the `mintplex-labs/anything-llm` application, specifically within the username parameter during the login process at the `/api/request-token` endpoint. The vulnerability arises from improper handling of values, allowing attackers to perform brute force attacks without prior knowledge of the username. Once the password is known, attackers can conduct blind attacks to ascertain the full username, significantly compromising system security.
The advisory is available at huntr.com. This vulnerability is traded as CVE-2024-3102 since 03/29/2024. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.
Upgrading to version 1.0.0 eliminates this vulnerability. Applying the patch 2374939ffb551ab2929d7f9d5827fe6597fa8caa 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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (huntr.dev): 🔍
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: Improper handling of valuesCWE: CWE-229 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: anything-llm 1.0.0
Patch: 2374939ffb551ab2929d7f9d5827fe6597fa8caa
Timeline
03/29/2024 🔍06/06/2024 🔍
06/06/2024 🔍
11/03/2024 🔍
Sources
Product: github.comAdvisory: huntr.com
Status: Confirmed
CVE: CVE-2024-3102 (🔍)
GCVE (CVE): GCVE-0-2024-3102
GCVE (VulDB): GCVE-100-267354
Entry
Created: 06/06/2024 21:39Updated: 11/03/2024 19:45
Changes: 06/06/2024 21:39 (67), 06/08/2024 04:37 (1), 11/03/2024 19:45 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.