Discourse-jira on Discourse insufficient control flow management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Discourse-jira on Discourse. Affected is an unknown function. The manipulation results in insufficient control flow management. This vulnerability is reported as CVE-2023-44384. The attack can be launched remotely. No exploit exists. A patch should be applied to remediate this issue.
Details
A vulnerability, which was classified as problematic, was found in Discourse-jira on Discourse (the affected version unknown). Affected is an unknown part. The manipulation with an unknown input leads to a insufficient control flow management vulnerability. CWE is classifying the issue as CWE-691. The code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways. This is going to have an impact on confidentiality. CVE summarizes:
Discourse-jira is a Discourse plugin allows Jira projects, issue types, fields and field options will be synced automatically. An administrator user can make an SSRF attack by setting the Jira URL to an arbitrary location and enabling the `discourse_jira_verbose_log` site setting. A moderator user could manipulate the request path to the Jira API, allowing them to perform arbitrary GET requests using the Jira API credentials, potentially with elevated permissions, used by the application.
The weakness was disclosed 10/07/2023 as GHSA-pmv5-h2x6-35fh. The advisory is available at github.com. This vulnerability is traded as CVE-2023-44384 since 09/28/2023. The technical details are unknown and an exploit is not available.
Applying the patch 8a2d3ad228883199fd5f081cc93d173c88e2e48f is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.4VulDB Meta Temp Score: 3.3
VulDB Base Score: 2.7
VulDB Temp Score: 2.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.1
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: Insufficient control flow managementCWE: CWE-691
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 8a2d3ad228883199fd5f081cc93d173c88e2e48f
Timeline
09/28/2023 🔍10/07/2023 🔍
10/07/2023 🔍
10/07/2023 🔍
Sources
Advisory: GHSA-pmv5-h2x6-35fhStatus: Confirmed
CVE: CVE-2023-44384 (🔍)
GCVE (CVE): GCVE-0-2023-44384
GCVE (VulDB): GCVE-100-241482
Entry
Created: 10/07/2023 08:18Changes: 10/07/2023 08:18 (49)
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.