API-key deletion via forged authenticated GET request
Published Aug 28, 2022 · Updated Aug 3, 2024
Cross-site request forgery in Froxlor before 0.10.38 allows remote attackers to delete a logged-in user's API key via a crafted request. The api_keys.php delete action accepts an id from the query string and immediately executes the matching DELETE without a confirmation POST. Exploitation requires an authenticated administrator or customer to follow an attacker-controlled link, and the bounded consequence is loss of the selected API credential.
Summary
What happened
Cross-site request forgery in Froxlor before 0.10.38 allows remote attackers to delete a logged-in user's API key via a crafted request. The api_keys.php delete action accepts an id from the query string and immediately executes the matching DELETE without a confirmation POST. Exploitation requires an authenticated administrator or customer to follow an attacker-controlled link, and the bounded consequence is loss of the selected API credential.
The record
- CVE
- CVE-2022-3017
- Published
- Aug 28, 2022
- Updated
- Aug 3, 2024
- Vendor
- Froxlor
- Product
- Froxlor
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2022CVE 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 <0.10.38
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 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