# CVE-2023-30607: icingaweb2-module-jira template and field configuration are susceptible to CSRF

> Attackers can force deletion of Jira template and field configurations in Icinga Web 2 without user consent due to missing CSRF validation.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Jul 2023
- **Updated:** 24 Oct 2024
- **Also known as:** GHSA-gh7w-7f7j-gwp5

## What is CVE-2023-30607?

CVE-2023-30607 is a medium-severity vulnerability in icingaweb2-module-jira, published on 5 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Icinga Icinga Web Jira Integration.

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

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

## Is CVE-2023-30607 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-30607 is a medium-severity vulnerability in icingaweb2-module-jira, published on 5 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-30607 in the wild and no public exploit code.

Affected product: icingaweb2-module-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-30607/ (Markdown: https://insights.sbomify.com/CVE-2023-30607/index.md)
```

## Sources

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

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