Unauthorized actions via cross-site request forgery
Published Feb 4, 2021 · Updated Sep 16, 2024
CSRF in IBM API Connect 2018.4.1.0 through 2018.4.1.13 and 10.0.0.0 through 10.0.1.0 lets attackers trigger unauthorized actions. IBM has not disclosed the affected request handler or the missing origin, token, or request-integrity check that permits a trusted browser to submit an attacker-chosen action. Exploitation requires a trusted user to transmit the crafted request; published impact is limited to unauthorized actions, without data disclosure or service interruption.
Summary
What happened
CSRF in IBM API Connect 2018.4.1.0 through 2018.4.1.13 and 10.0.0.0 through 10.0.1.0 lets attackers trigger unauthorized actions. IBM has not disclosed the affected request handler or the missing origin, token, or request-integrity check that permits a trusted browser to submit an attacker-chosen action. Exploitation requires a trusted user to transmit the crafted request; published impact is limited to unauthorized actions, without data disclosure or service interruption.
The record
- CVE
- CVE-2020-4826
- Published
- Feb 4, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- API Connect
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 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=10.0.0.0
- Affected versionversion=10.0.1.0
- Affected versionversion=2018.4.1.0
- Affected versionversion=2018.4.1.13
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