Icinga Web Jira Integration
Approved changes feed: RSS · Atom
cpe:2.3:a:icinga:icinga_web_jira_integration:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Icinga (f3c2076d-deab-53f8-8d1d-6154f519c3cc) |
|---|---|
| Product | Icinga Web Jira Integration (da4b4dd4-c049-5ec1-a205-250385254f82) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/icinga/icingaweb2-module-jira |
purl2cpe | 2026-06-01 10:11:14.145600 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-30607 |
vulnerable | 2026-06-03 14:51:52.826420 |
icingaweb2-module-jira template and field configuration are susceptible to CSRF
MEDIUM (5)
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.
Published: 2023-07-05T17:42:54.496Z
Updated: 2024-10-24T19:06:17.105Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.