Reminder-email dispatch via state-changing GET request
Published Oct 11, 2023 · Updated Sep 18, 2024
Cross-site request forgery in Snipe-IT before 6.2.3 allows remote attackers to send asset-acceptance reminder emails. The unaccepted-assets report exposed reminder dispatch as a GET route with the acceptance identifier in the URL, so a browser request performed the state-changing action without a CSRF token. Exploitation requires an authenticated victim with reports-view permission to load a crafted request, which sends an unsolicited reminder to the asset assignee.
Summary
What happened
Cross-site request forgery in Snipe-IT before 6.2.3 allows remote attackers to send asset-acceptance reminder emails. The unaccepted-assets report exposed reminder dispatch as a GET route with the acceptance identifier in the URL, so a browser request performed the state-changing action without a CSRF token. Exploitation requires an authenticated victim with reports-view permission to load a crafted request, which sends an unsolicited reminder to the asset assignee.
The record
- CVE
- CVE-2023-5511
- Published
- Oct 11, 2023
- Updated
- Sep 18, 2024
- Vendor
- Grokability, Inc.
- Product
- Snipe-IT
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2023CVE publishedPublication date reported by the CVE source.
- Sep 18, 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 <6.2.3
- Affected versionversion=unspecified <v.6.2.3
What conditions does exploitation require?
What is affected?
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
- huntr.dev CSRF proof of conceptproof of concept · unverified
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