Cross-organizer e-mail disclosure via unchecked event identifier
Published Feb 19, 2024 · Updated Aug 1, 2024
Improper access control in alf.io before 2.0-M4-2402 allows remote authenticated users to read other organizers' e-mail logs. EmailMessageApiController accepts an event identifier in an admin e-mail-log request without verifying that the requesting principal can access that event. An account with back-office access to one organizer can substitute another event's identifier and receive that event's e-mail-log records.
Summary
What happened
Improper access control in alf.io before 2.0-M4-2402 allows remote authenticated users to read other organizers' e-mail logs. EmailMessageApiController accepts an event identifier in an admin e-mail-log request without verifying that the requesting principal can access that event. An account with back-office access to one organizer can substitute another event's identifier and receive that event's e-mail-log records.
The record
- CVE
- CVE-2024-25634
- Published
- Feb 19, 2024
- Updated
- Aug 1, 2024
- Vendor
- Alf.io
- Product
- alf.io
- Classifications
- CWE-497, T1213
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Feb 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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
- Cross-organizer e-mail-log request 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