Unauthorized actions via improper CSRF checking
Published Aug 2, 2021 · Updated Sep 16, 2024
Cross-site request forgery in IBM QRadar User Entity Behavior Analytics 4.1.1 allows remote attackers to perform unauthorized actions. IBM identifies improper CSRF checks in some components but does not disclose the affected endpoints or validation operation. Exploitation requires an authenticated user to submit the attacker's request; IBM bounds the published impact to unauthorized state changes without confidentiality or availability loss.
Summary
What happened
Cross-site request forgery in IBM QRadar User Entity Behavior Analytics 4.1.1 allows remote attackers to perform unauthorized actions. IBM identifies improper CSRF checks in some components but does not disclose the affected endpoints or validation operation. Exploitation requires an authenticated user to submit the attacker's request; IBM bounds the published impact to unauthorized state changes without confidentiality or availability loss.
The record
- CVE
- CVE-2021-29757
- Published
- Aug 2, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM QRadar User Entity Behavior Analytics
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 2, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=4.1.1
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