Cross-organization data access via unchecked user identifier
Published Feb 19, 2024 · Updated Aug 28, 2024
Improper authorization in alf.io before 2.0-M4-2402 allows remote authenticated users to read other organizations' user and API-key data. The GET /admin/api/users/{user_id} handler accepts an arbitrary numeric user identifier and returns the matching record without limiting it to the requester's organization. Organization-owner access and a multi-tenant deployment are required; a disclosed API key grants access to and modification of another organization's data.
Summary
What happened
Improper authorization in alf.io before 2.0-M4-2402 allows remote authenticated users to read other organizations' user and API-key data. The GET /admin/api/users/{user_id} handler accepts an arbitrary numeric user identifier and returns the matching record without limiting it to the requester's organization. Organization-owner access and a multi-tenant deployment are required; a disclosed API key grants access to and modification of another organization's data.
The record
- CVE
- CVE-2024-25635
- Published
- Feb 19, 2024
- Updated
- Aug 28, 2024
- Vendor
- Alf.io
- Product
- alf.io
- Classifications
- CWE-612, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 28, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.0-M4-2402
- Affected versionversion=< 2.0-M4-2402
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA authenticated cross-organization user lookup proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo