Unauthorized actions via forged trusted-user requests
Published Feb 4, 2021 · Updated Sep 17, 2024
CSRF in IBM API Connect 10.0.0.0 through 10.0.1.0 and 2018.4.1.0 through 2018.4.1.13 allows remote attackers to perform unauthorized actions. IBM identifies the management server as affected but has not disclosed the request endpoint or the missing validation operation. A victim must submit the forged request within a trusted management-server session; the published impact is unauthorized state-changing action.
Summary
What happened
CSRF in IBM API Connect 10.0.0.0 through 10.0.1.0 and 2018.4.1.0 through 2018.4.1.13 allows remote attackers to perform unauthorized actions. IBM identifies the management server as affected but has not disclosed the request endpoint or the missing validation operation. A victim must submit the forged request within a trusted management-server session; the published impact is unauthorized state-changing action.
The record
- CVE
- CVE-2020-4827
- Published
- Feb 4, 2021
- Updated
- Sep 17, 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 17, 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?
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