Investigation report deletion via forged request
Published Mar 3, 2024 · Updated Aug 5, 2024
Cross-site request forgery in Bdtask Hospital Automanager 20240223 allows remote attackers to delete investigation reports via a forged request. The /investigation/delete/ endpoint processes a state-changing deletion request without sufficient proof that the logged-in user intended it. Exploitation requires a logged-in user with report-deletion authority to submit the attacker-controlled request, and the bounded consequence is deletion of an investigation report.
Summary
What happened
Cross-site request forgery in Bdtask Hospital Automanager 20240223 allows remote attackers to delete investigation reports via a forged request. The /investigation/delete/ endpoint processes a state-changing deletion request without sufficient proof that the logged-in user intended it. Exploitation requires a logged-in user with report-deletion authority to submit the attacker-controlled request, and the bounded consequence is deletion of an investigation report.
The record
- CVE
- CVE-2024-2134
- Published
- Mar 3, 2024
- Updated
- Aug 5, 2024
- Vendor
- Bdtask
- Product
- Hospital Automanager
- Classifications
- CWE-352, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 3, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=20240223
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.
Public exploit references
- VulDB-referenced Google Drive exploit artifactproof 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