Vulnerability in icingaweb2-module-reporting (DEBIAN-CVE-2025-27406)

Summary

Vulnerability in icingaweb2-module-reporting (DEBIAN-CVE-2025-27406). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.0.4-1 or later.

Original description

The description as published by the source.

Icinga Reporting is the central component for reporting related functionality in the monitoring web frontend and framework Icinga Web 2. A vulnerability present in versions 0.10.0 through 1.0.2 allows to set up a template that allows to embed arbitrary Javascript. This enables the attacker to act on behalf of the user, if the template is being previewed; and act on behalf of the headless browser, if a report using the template is printed to PDF. This issue has been resolved in version 1.0.3 of Icinga Reporting. As a workaround, review all templates and remove suspicious settings.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as DEBIAN-CVE-2025-27406 has been found in icingaweb2-module-reporting.
Successful exploitation can lead to full system takeover.
What to do: upgrade icingaweb2-module-reporting to 1.0.4-1 or later.
If unsure, ask your IT team or search "icingaweb2-module-reporting DEBIAN-CVE-2025-27406" on the vendor's site.

DEBIAN-CVE-2025-27406 (icingaweb2-module-reporting)
Attack vector: remote (network-reachable)
Patched: 1.0.4-1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in icingaweb2-module-reporting.

📍 Affected scope

Check the vendor advisory for the affected versions of icingaweb2-module-reporting.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.0.4-1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'icingaweb2-module-reporting' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'icingaweb2-module-reporting' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で icingaweb2-module-reporting を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade icingaweb2-module-reporting to 1.0.4-1
```
ステージング環境で 1.0.4-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:12 icingaweb2-module-reporting

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Debian:13 icingaweb2-module-reporting

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.4-1"}]}]

Debian:14 icingaweb2-module-reporting

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.4-1"}]}]

References

advisory security-tracker.debian.org