CVE-2017-6080

Description

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.

Category

9.8
CVSS
Severity: Critical
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.17%
Vendor Advisory zammad.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
http://www.securityfocus.com/bid/96937 third party advisory vdb entry
https://zammad.com/de/news/security-advisory-zaa-2017-01 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2017-6080?
CVE-2017-6080 has been scored as a critical severity vulnerability.
How to fix CVE-2017-6080?
To fix CVE-2017-6080, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-6080 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-6080 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.