Backend data access via SQL injection
Published Oct 6, 2021 · Updated Sep 17, 2024
SQL injection in IBM Sterling B2B Integrator 6.0.0.0 through 6.1.1.0 allows remote attackers to read or alter back-end database data. IBM documents specially crafted SQL statements reaching the back-end database but does not identify the vulnerable endpoint or query operation. The CVSS record requires low-privilege network access without user interaction; successful exploitation can view, add, modify, or delete database information.
Summary
What happened
SQL injection in IBM Sterling B2B Integrator 6.0.0.0 through 6.1.1.0 allows remote attackers to read or alter back-end database data. IBM documents specially crafted SQL statements reaching the back-end database but does not identify the vulnerable endpoint or query operation. The CVSS record requires low-privilege network access without user interaction; successful exploitation can view, add, modify, or delete database information.
The record
- CVE
- CVE-2021-29798
- Published
- Oct 6, 2021
- Updated
- Sep 17, 2024
- Vendor
- IBM
- Product
- IBM Sterling B2B Integrator
- Classifications
- T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 6, 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=6.0.0.0
- Affected versionversion=6.0.3.4
- Affected versionversion=6.1.0.0
- Affected versionversion=6.1.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