This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2022-2400 →

UBUNTU-CVE-2022-2400

Vulnerability in civicrm (UBUNTU-CVE-2022-2400)

Summary

Vulnerability in civicrm (UBUNTU-CVE-2022-2400). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.6.1+dfsg-2ubuntu1+esm1 or later.

Original description

The description as published by the source.

External Control of File Name or Path in GitHub repository dompdf/dompdf prior to 2.0.0.

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 weakness called UBUNTU-CVE-2022-2400 was discovered in civicrm.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "civicrm UBUNTU-CVE-2022-2400".

UBUNTU-CVE-2022-2400 (civicrm). Severity: Info.
Response plan:

Check the vendor advisory for affected versions and the patched release.
If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.

❓ What is the problem

A weakness (UBUNTU-CVE-2022-2400) in civicrm. A serious software flaw has been identified.

📍 Affected scope

Target versions of civicrm (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: Info. Low severity or not yet rated.

🔧 How to fix

Update to the patched release as listed in the vendor advisory.

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.

Response actions

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

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