mintplex-labs anything-llm up to 0.x Password Hash /api/request-token exposure of sensitive information through metadata
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.9 | $0-$5k | 0.00 |
A vulnerability was found in mintplex-labs anything-llm up to 0.x. It has been rated as problematic. Affected by this issue is an unknown functionality of the file /api/request-token of the component Password Hash Handler. The manipulation with an unknown input leads to a exposure of sensitive information through metadata vulnerability. Using CWE to declare the problem leads to CWE-1230. The product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from the original, sensitive information. Impacted is confidentiality. CVE summarizes:
In mintplex-labs/anything-llm versions up to and including 1.5.3, an issue was discovered where the password hash of a user is returned in the response after login (`POST /api/request-token`) and after account creations (`POST /api/admin/users/new`). This exposure occurs because the entire User object, including the bcrypt password hash, is included in the response sent to the frontend. This practice could potentially lead to sensitive information exposure despite the use of bcrypt, a strong hashing algorithm. It is recommended not to expose any clues about passwords to the frontend.
The advisory is shared for download at huntr.com. This vulnerability is handled as CVE-2024-5213 since 05/22/2024. The exploitation is known to be difficult. The attack may be launched remotely. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
Upgrading to version 1.0.0 eliminates this vulnerability. Applying the patch 9df4521113ddb9a3adb5d0e3941e7d494992629c 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
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.9
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: Exposure of sensitive information through metadataCWE: CWE-1230 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
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: 9df4521113ddb9a3adb5d0e3941e7d494992629c
Timeline
05/22/2024 CVE reserved06/20/2024 Advisory disclosed
06/20/2024 VulDB entry created
07/17/2024 VulDB entry last update
Sources
Advisory: huntr.comStatus: Confirmed
CVE: CVE-2024-5213 (🔒)
GCVE (CVE): GCVE-0-2024-5213
GCVE (VulDB): GCVE-100-269144
Entry
Created: 06/20/2024 06:53 AMUpdated: 07/17/2024 07:02 PM
Changes: 06/20/2024 06:53 AM (66), 07/17/2024 07:02 PM (13)
Complete: 🔍
Cache ID: 18:7FC:40
No comments yet. Languages: en.
Please log in to comment.