Two-factor authentication changes via missing CSRF validation
Published Jun 2, 2023 · Updated Feb 6, 2025
CSRF in coreBOS before 8 allows remote attackers to change a user's two-factor authentication setting through a forged request. The 2FA integration handler processes setconfig2fa requests and writes the User_2FAAuthentication setting without validating a CSRF token. Exploitation requires a logged-in user to submit an attacker-controlled request, and the resulting state change can disable or enable that user's two-factor authentication.
Summary
What happened
CSRF in coreBOS before 8 allows remote attackers to change a user's two-factor authentication setting through a forged request. The 2FA integration handler processes setconfig2fa requests and writes the User_2FAAuthentication setting without validating a CSRF token. Exploitation requires a logged-in user to submit an attacker-controlled request, and the resulting state change can disable or enable that user's two-factor authentication.
The record
- CVE
- CVE-2023-3075
- Published
- Jun 2, 2023
- Updated
- Feb 6, 2025
- Vendor
- TSolucio
- Product
- coreBOS
- Classifications
- CWE-352, T1556.006
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2023CVE publishedPublication date reported by the CVE source.
- Feb 6, 2025Record 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 <8
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