Unauthorized actions via forged trusted-session requests
Published Jul 30, 2024 · Updated Aug 2, 2024
Cross-site request forgery in IBM Aspera Orchestrator 4.0.1 and earlier allows attackers to perform unauthorized actions via crafted requests. IBM has not disclosed the affected request handler or the missing anti-CSRF validation that permits a trusted user session to accept attacker-controlled requests. Exploitation requires user interaction and an authenticated browser session trusted by Orchestrator; resulting changes are limited to actions available to that session.
Summary
What happened
Cross-site request forgery in IBM Aspera Orchestrator 4.0.1 and earlier allows attackers to perform unauthorized actions via crafted requests. IBM has not disclosed the affected request handler or the missing anti-CSRF validation that permits a trusted user session to accept attacker-controlled requests. Exploitation requires user interaction and an authenticated browser session trusted by Orchestrator; resulting changes are limited to actions available to that session.
The record
- CVE
- CVE-2023-38001
- Published
- Jul 30, 2024
- Updated
- Aug 2, 2024
- Vendor
- IBM
- Product
- Aspera Orchestrator
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2024CVE 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=4.0.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