CSRF in Zammad
CVE-2017-6080
An issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1, caused by lack of a protection mechanism involving HTTP Access-Control headers. To exploit the vulnerability, an attacker can send cross-domain requests directly to the REST API for users with a valid session cookie and receive the result.
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS: 0.007 (52.3th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 52nd percentile — 52.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.007 · newest: 0.007 · change: 0.000
Affected products
- Zammad — versions 1.1.0, 1.1.1, 1.1.2
Weakness classification (CWE)
References
- www.securityfocus.com/bid/96937 (VDB Entry, Third Party Advisory, vdb-entry)
- zammad.com/de/news/security-advisory-zaa-2017-01 (Vendor Advisory)
Frequently asked questions
- What is CVE-2017-6080?
- CVE-2017-6080 is a critical-severity vulnerability in Zammad, classified under Cross-Site Request Forgery (CSRF). CVSS score: 9.8/10. Published 2017-03-13.
- How severe is CVE-2017-6080?
- Critical severity. CVSS v3 base score is 9.8 out of 10.