alf.io 2.0-M4-2301/2.0-M4-2304 API Endpoint /admin/api/users/ improper authorization of index containing sensitive information
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in alf.io. Affected by this issue is some unknown functionality of the file /admin/api/users/ of the component API Endpoint. The manipulation leads to improper authorization of index containing sensitive information. This vulnerability is listed as CVE-2024-25635. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability was found in alf.io. It has been rated as critical. This issue affects some unknown functionality of the file /admin/api/users/ of the component API Endpoint. The manipulation with an unknown input leads to a improper authorization of index containing sensitive information vulnerability. Using CWE to declare the problem leads to CWE-612. The product creates a search index of private or sensitive documents, but it does not properly limit index access to actors who are authorized to see the original information. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
alf.io is an open source ticket reservation system. Prior to version 2.0-Mr-2402, organization owners can view the generated API KEY and USERS of other organization owners using the `http://192.168.26.128:8080/admin/api/users/` endpoint, which exposes the details of the provided user ID. This may also expose the API KEY in the username of the user. Version 2.0-M4-2402 fixes this issue.
The weakness was presented 02/20/2024 as GHSA-ffr5-g3qg-gp4f. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2024-25635 since 02/08/2024. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Upgrading to version 2.0-M4-2402 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CNA Base Score: 8.8
CNA Vector (GitHub, Inc.): 🔍
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 authorization of index containing sensitive informationCWE: CWE-612
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: alf.io 2.0-M4-2402
Timeline
02/08/2024 🔍02/20/2024 🔍
02/20/2024 🔍
12/18/2024 🔍
Sources
Advisory: GHSA-ffr5-g3qg-gp4fStatus: Confirmed
CVE: CVE-2024-25635 (🔍)
GCVE (CVE): GCVE-0-2024-25635
GCVE (VulDB): GCVE-100-254123
Entry
Created: 02/20/2024 07:25Updated: 12/18/2024 19:03
Changes: 02/20/2024 07:25 (49), 12/18/2024 19:03 (27)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.