Forced logout via tokenless GET request
Published Dec 11, 2021 · Updated Aug 3, 2024
Cross-site request forgery in YetiForce CRM before 6.3.0 allows remote attackers to terminate an authenticated user's session. The logout action accepts a GET request without an anti-CSRF token, so the browser attaches the victim's session and the server processes an unintended logout. Exploitation requires an authenticated victim to follow or load an attacker-controlled request, and the demonstrated consequence is forced logout rather than data access.
Summary
What happened
Cross-site request forgery in YetiForce CRM before 6.3.0 allows remote attackers to terminate an authenticated user's session. The logout action accepts a GET request without an anti-CSRF token, so the browser attaches the victim's session and the server processes an unintended logout. Exploitation requires an authenticated victim to follow or load an attacker-controlled request, and the demonstrated consequence is forced logout rather than data access.
The record
- CVE
- CVE-2021-4092
- Published
- Dec 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- YetiForce
- Product
- YetiForce CRM
- Classifications
- CWE-352, CAPEC-62, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 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 <6.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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