Application log deletion via tokenless flush request
Published Nov 19, 2021 · Updated Aug 3, 2024
Cross-site request forgery in Kimai before 1.16.2 allows remote attackers to delete its application log through an administrator's browser. The DoctorController flush-log GET route accepts a logged-in request without verifying a CSRF token and then deletes the configured log file. A victim must hold the system_configuration permission and load an attacker-controlled request; the bounded consequence is deletion of the current application log.
Summary
What happened
Cross-site request forgery in Kimai before 1.16.2 allows remote attackers to delete its application log through an administrator's browser. The DoctorController flush-log GET route accepts a logged-in request without verifying a CSRF token and then deletes the configured log file. A victim must hold the system_configuration permission and load an attacker-controlled request; the bounded consequence is deletion of the current application log.
The record
- CVE
- CVE-2021-3957
- Published
- Nov 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Kevin Papst
- Product
- Kimai
- Classifications
- CWE-352, CAPEC-62, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 19, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=unspecified <1.16.2
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
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