Zammad up to 1.0.3/1.1.2/1.2.0 REST API cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Zammad up to 1.0.3/1.1.2/1.2.0. Impacted is an unknown function of the component REST API. The manipulation leads to cross-site request forgery. This vulnerability is listed as CVE-2017-6081. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability was found in Zammad up to 1.0.3/1.1.2/1.2.0. It has been rated as problematic. This issue affects some unknown functionality of the component REST API. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. The summary by CVE is:
A CSRF issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1. To exploit the vulnerability, an attacker can send cross-domain requests directly to the REST API for users with a valid session cookie.
The bug was discovered 02/14/2017. The weakness was presented 03/13/2017 by Lukas Reschke (Website). It is possible to read the advisory at zammad.com. The identification of this vulnerability is CVE-2017-6081 since 02/18/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 27 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 1.0.4, 1.1.3 or 1.2.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 96937†). See VDB-97876, VDB-97877, VDB-97878 and VDB-97882 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Zammad 1.0.4/1.1.3/1.2.1
Timeline
02/14/2017 🔍02/18/2017 🔍
03/13/2017 🔍
03/13/2017 🔍
03/13/2017 🔍
03/13/2017 🔍
09/06/2020 🔍
Sources
Advisory: zammad.comResearcher: Lukas Reschke
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-6081 (🔍)
GCVE (CVE): GCVE-0-2017-6081
GCVE (VulDB): GCVE-100-97883
SecurityFocus: 96937 - Zammad Multiple Security Vulnerabilities
OSVDB: - CVE-2017-6081 - Zammad - Cross-Site Request Forgery Issue
See also: 🔍
Entry
Created: 03/13/2017 13:28Updated: 09/06/2020 11:46
Changes: 03/13/2017 13:28 (60), 09/06/2020 11:46 (6)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.