Unauthorized actions via forged trusted-user requests
Published Jul 19, 2022 · Updated Sep 16, 2024
CSRF in IBM Sterling Partner Engagement Manager 6.1.2, 6.2, and Cloud/SaaS 22.2 allows remote attackers to perform unauthorized actions. IBM has not identified the affected request handler or disclosed which request-validation operation fails to reject attacker-supplied requests. Exploitation requires an authenticated user's browser to submit an attacker-controlled request, changing application data or state without that user's intent.
Summary
What happened
CSRF in IBM Sterling Partner Engagement Manager 6.1.2, 6.2, and Cloud/SaaS 22.2 allows remote attackers to perform unauthorized actions. IBM has not identified the affected request handler or disclosed which request-validation operation fails to reject attacker-supplied requests. Exploitation requires an authenticated user's browser to submit an attacker-controlled request, changing application data or state without that user's intent.
The record
- CVE
- CVE-2022-22359
- Published
- Jul 19, 2022
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Sterling Partner Engagement Manager
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2022CVE 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=6.1.2
- Affected versionversion=6.2
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