Information disclosure via verbose Job History errors
Published May 24, 2021 · Updated Sep 16, 2024
Information exposure in IBM Security Guardium 10.5 through 11.3 allows remote attackers to read sensitive data through browser errors. The Job History report returns a detailed technical error message to the browser instead of suppressing internal details. No authentication or user interaction is required; disclosed details can support further attacks, but IBM does not identify the exact data exposed.
Summary
What happened
Information exposure in IBM Security Guardium 10.5 through 11.3 allows remote attackers to read sensitive data through browser errors. The Job History report returns a detailed technical error message to the browser instead of suppressing internal details. No authentication or user interaction is required; disclosed details can support further attacks, but IBM does not identify the exact data exposed.
The record
- CVE
- CVE-2021-20428
- Published
- May 24, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Security Guardium
- Classifications
- CWE-209
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 24, 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=11.2
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