Sensitive-data exposure via browser memory caching
Published Mar 5, 2020 · Updated Aug 4, 2024
Sensitive-data exposure in Zammad 1.0.x through 3.2.0 allows attackers to read confidential information from browser memory. The application fails to prevent confidential data from remaining in the browser cache, where cached contents can be browsed outside an authenticated Zammad session. Access requires remote compromise of, or physical access to, a user's workstation; disclosure is limited to sensitive information retained in that cache.
Summary
What happened
Sensitive-data exposure in Zammad 1.0.x through 3.2.0 allows attackers to read confidential information from browser memory. The application fails to prevent confidential data from remaining in the browser cache, where cached contents can be browsed outside an authenticated Zammad session. Access requires remote compromise of, or physical access to, a user's workstation; disclosure is limited to sensitive information retained in that cache.
The record
- CVE
- CVE-2020-10096
- Published
- Mar 5, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200, T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 5, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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