Unauthenticated source disclosure via OPTIONS response
Published Mar 5, 2020 · Updated Aug 4, 2024
Source code disclosure in Zammad 1.0.0 through 3.2.0 allows remote attackers to read static-resource source via an OPTIONS request. The static-resource handler returns the contents of /zammad/public/404.html for OPTIONS instead of limiting the response to method metadata. No authentication or user interaction is required; the disclosed template source reveals implementation details that support more precise follow-on attacks.
Summary
What happened
Source code disclosure in Zammad 1.0.0 through 3.2.0 allows remote attackers to read static-resource source via an OPTIONS request. The static-resource handler returns the contents of /zammad/public/404.html for OPTIONS instead of limiting the response to method metadata. No authentication or user interaction is required; the disclosed template source reveals implementation details that support more precise follow-on attacks.
The record
- CVE
- CVE-2020-10105
- Published
- Mar 5, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-552, T1190
- Attack vector
- network
- 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