Audit configuration changes via missing CSRF validation
Published Jan 14, 2022 · Updated Aug 2, 2024
Cross-site request forgery in Live Helper Chat before 2.0 allows remote attackers to alter audit settings through a crafted request. The lhaudit configuration handler processes StoreOptions POST data and saves audit_configuration without validating a CSRF token. Exploitation requires an authenticated administrator to submit an attacker-controlled request, allowing changes to audit logging settings.
Summary
What happened
Cross-site request forgery in Live Helper Chat before 2.0 allows remote attackers to alter audit settings through a crafted request. The lhaudit configuration handler processes StoreOptions POST data and saves audit_configuration without validating a CSRF token. Exploitation requires an authenticated administrator to submit an attacker-controlled request, allowing changes to audit logging settings.
The record
- CVE
- CVE-2022-0226
- Published
- Jan 14, 2022
- Updated
- Aug 2, 2024
- Vendor
- LiveHelperChat
- Product
- Live Helper Chat
- Classifications
- CWE-352, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 <2.0
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
- Audit configuration request without CSRF tokenproof of concept · demonstrated
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