{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-44384 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-44384 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2023-44384 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2023-44384 in the wild and no public exploit code.\n\nAffected product: discourse-jira. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-44384/ (Markdown: https://insights.sbomify.com/CVE-2023-44384/index.md)","id":"CVE-2023-44384","markdown":"https://insights.sbomify.com/CVE-2023-44384/index.md","name":"CVE-2023-44384","record":{"aliases":["GHSA-pmv5-h2x6-35fh"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Discourse Jira plugin","requires_auth":"high_privilege","summary":"An administrator can trigger SSRF by configuring the Jira URL, while moderators can manipulate API paths to perform unauthorized requests.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"discourse_jira","vendor":"discourse"}],"cvss":{"score":4.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-691","name":"Insufficient Control Flow Management"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Discourse-Jira could make SSRF attack by setting Jira URL to an arbitrary location","id":"CVE-2023-44384","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Client-Side Request Forgery in Home Assistant iOS/macOS native Apps","id":"CVE-2023-44385"},"packages":[],"prev":{"headline":"October CMS stored XSS by authenticated backend user with improper configuration","id":"CVE-2023-44383"},"products":["discourse-jira"],"published":"2023-10-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-19","vendors":["discourse"]},"summary":"An administrator can trigger SSRF by configuring the Jira URL, while moderators can manipulate API paths to perform unauthorized requests.","url":"https://insights.sbomify.com/CVE-2023-44384/"}