Unauthorized dashboard actions via forged requests
Published Jan 31, 2025 · Updated Jan 31, 2025
CSRF in IBM Sterling B2B Integrator 6.0.0.0 through 6.1.2.5 allows remote attackers to submit unauthorized Dashboard UI actions. IBM identifies the Dashboard UI as the affected component but has not disclosed the endpoint or the request-validation operation that fails. Versions 6.2.0.0 through 6.2.0.3 are also affected; exploitation requires interaction from a user with an authenticated Dashboard session, and actions execute with that user's authority.
Summary
What happened
CSRF in IBM Sterling B2B Integrator 6.0.0.0 through 6.1.2.5 allows remote attackers to submit unauthorized Dashboard UI actions. IBM identifies the Dashboard UI as the affected component but has not disclosed the endpoint or the request-validation operation that fails. Versions 6.2.0.0 through 6.2.0.3 are also affected; exploitation requires interaction from a user with an authenticated Dashboard session, and actions execute with that user's authority.
The record
- CVE
- CVE-2023-38739
- Published
- Jan 31, 2025
- Updated
- Jan 31, 2025
- Vendor
- IBM
- Product
- IBM Sterling B2B Integrator
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 31, 2025CVE publishedPublication date reported by the CVE source.
- Jan 31, 2025Record 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.0.0.0 <=6.1.2.5
- Affected versionversion=6.2.0.0 <=6.2.0.3
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