Sensitive-data disclosure via unreviewed Bugzilla crash reports
Published Jan 31, 2020 · Updated Aug 6, 2024
Information disclosure in ABRT 2.0.8 allows attackers to obtain sensitive data from crash reports submitted to Bugzilla. ABRT's reporting interface does not let users search all collected crash data for sensitive content before a Bugzilla submission. Only users who send reports to Red Hat Bugzilla encounter this exposure; the default Red Hat Customer Support destination is unaffected.
Summary
What happened
Information disclosure in ABRT 2.0.8 allows attackers to obtain sensitive data from crash reports submitted to Bugzilla. ABRT's reporting interface does not let users search all collected crash data for sensitive content before a Bugzilla submission. Only users who send reports to Red Hat Bugzilla encounter this exposure; the default Red Hat Customer Support destination is unaffected.
The record
- CVE
- CVE-2011-4088
- Published
- Jan 31, 2020
- Updated
- Aug 6, 2024
- Vendor
- ABRT Project
- Product
- ABRT
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 31, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=2.0.8
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