Zammad up to 4.1.0 GitHub/GitLab server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Zammad up to 4.1.0. Affected by this vulnerability is an unknown functionality of the component GitHub/GitLab. The manipulation leads to server-side request forgery. This vulnerability is referenced as CVE-2021-42091. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Zammad up to 4.1.0. It has been rated as critical. This issue affects some unknown processing of the component GitHub/GitLab. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality, integrity, and availability.
The weakness was published 10/08/2021 as zaa-2021-08. The advisory is shared at zammad.com. The identification of this vulnerability is CVE-2021-42091 since 10/07/2021. Neither technical details nor an exploit are publicly available.
Upgrading to version 4.1.1 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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 4.1.1
Timeline
10/07/2021 🔍10/08/2021 🔍
10/08/2021 🔍
10/14/2021 🔍
Sources
Advisory: zaa-2021-08Status: Confirmed
CVE: CVE-2021-42091 (🔍)
GCVE (CVE): GCVE-0-2021-42091
GCVE (VulDB): GCVE-100-184085
Entry
Created: 10/08/2021 09:51Updated: 10/14/2021 08:13
Changes: 10/08/2021 09:51 (39), 10/14/2021 08:13 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.