Unauthorized event contact via missing ACL check
Published Jun 30, 2020 · Updated Aug 4, 2024
Missing authorization in MISP 2.4.128 allows remote authenticated users to send contact requests for events they cannot access. EventsController::contact() checked only whether a supplied event identifier existed instead of fetching the event through the requesting user's ACL. A valid MISP account and an inaccessible event identifier are required; the action sends an event contact email without granting event visibility.
Summary
What happened
Missing authorization in MISP 2.4.128 allows remote authenticated users to send contact requests for events they cannot access. EventsController::contact() checked only whether a supplied event identifier existed instead of fetching the event through the requesting user's ACL. A valid MISP account and an inaccessible event identifier are required; the action sends an event contact email without granting event visibility.
The record
- CVE
- CVE-2020-15412
- Published
- Jun 30, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
No public exploit references are available in this record.
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