icingaweb2-module-jira 1.3.0/1.3.1 on Jira cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in icingaweb2-module-jira 1.3.0/1.3.1 on Jira. Impacted is an unknown function. Such manipulation leads to cross-site request forgery. This vulnerability is listed as CVE-2023-30607. The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability was found in icingaweb2-module-jira 1.3.0/1.3.1 on Jira (Atlassian Jira App Software). It has been rated as problematic. Affected by this issue is some unknown functionality. 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. CVE summarizes:
icingaweb2-module-jira provides integration with Atlassian Jira. Starting in version 1.3.0 and prior to version 1.3.2, template and field configuration forms perform the deletion action before user input is validated, including the cross site request forgery token. This issue is fixed in version 1.3.2. There are no known workarounds.
The weakness was presented 07/05/2023 as GHSA-gh7w-7f7j-gwp5. The advisory is available at github.com. This vulnerability is handled as CVE-2023-30607 since 04/13/2023. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available.
Upgrading to version 1.3.2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 7f0c53b7a3e87be2f4c2e8840805d7b7c9762424 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 6.0
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CNA Base Score: 5.0
CNA Vector (GitHub, Inc.): 🔍
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: 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: icingaweb2-module-jira 1.3.2
Patch: 7f0c53b7a3e87be2f4c2e8840805d7b7c9762424
Timeline
04/13/2023 🔍07/05/2023 🔍
07/05/2023 🔍
07/23/2023 🔍
Sources
Advisory: GHSA-gh7w-7f7j-gwp5Status: Confirmed
CVE: CVE-2023-30607 (🔍)
GCVE (CVE): GCVE-0-2023-30607
GCVE (VulDB): GCVE-100-233018
Entry
Created: 07/05/2023 20:26Updated: 07/23/2023 14:25
Changes: 07/05/2023 20:26 (54), 07/23/2023 14:25 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.