# CVE-2023-44384: Discourse-Jira could make SSRF attack by setting Jira URL to an arbitrary location

> An administrator can trigger SSRF by configuring the Jira URL, while moderators can manipulate API paths to perform unauthorized requests.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2023
- **Updated:** 19 Sep 2024
- **Also known as:** GHSA-pmv5-h2x6-35fh

## What is CVE-2023-44384?

CVE-2023-44384 is a medium-severity server-side request forgery vulnerability in discourse-jira, published on 6 Oct 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-691 (Insufficient Control Flow Management)

## Which versions are affected by CVE-2023-44384?

It affects 1 product.


Products: Discourse Discourse Jira.

## How do I fix CVE-2023-44384?

No fix has been published for CVE-2023-44384 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-44384 being exploited?

There is no known exploitation of CVE-2023-44384 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-44384 and fix it if it is affected.

What it is: CVE-2023-44384 is a medium-severity server-side request forgery vulnerability in discourse-jira, published on 6 Oct 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-44384 in the wild and no public exploit code.

Affected product: discourse-jira. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-44384/ (Markdown: https://insights.sbomify.com/CVE-2023-44384/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-44384
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-44384
- OSV: https://osv.dev/vulnerability/CVE-2023-44384

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-44384/
Summaries are generated and may contain mistakes; the official description above is the record.