Vulnerability in digikam (USN-7266-1)

Summary

vulnerability in digikam (USN-7266-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `4:4.12.0-0ubuntu7+esm1` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **USN-7266-1** has been found in digikam. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade digikam to **4:4.12.0-0ubuntu7+esm1** or later. If unsure, ask your IT team or search "digikam USN-7266-1" on the vendor's site.

USN-7266-1 (digikam) — Patched: `4:4.12.0-0ubuntu7+esm1` — 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 digikam.

📍 Affected scope

digikam — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **4:4.12.0-0ubuntu7+esm1**.

🛡️ 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 'digikam' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

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

Affected packages

Ubuntu:Pro:16.04:LTS digikam

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4:4.12.0-0ubuntu7+esm1"}]}]

Ubuntu:Pro:18.04:LTS digikam

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4:5.6.0-0ubuntu10+esm1"}]}]

Ubuntu:Pro:20.04:LTS digikam

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4:6.4.0+dfsg-3ubuntu0.1~esm1"}]}]

Ubuntu:Pro:22.04:LTS digikam

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4:7.5.0-3ubuntu0.1~esm1"}]}]

References

advisory https://ubuntu.com/security/notices/USN-7266-1
report https://ubuntu.com/security/CVE-2017-0691
report https://ubuntu.com/security/CVE-2020-19858
report https://ubuntu.com/security/CVE-2020-22628
report https://ubuntu.com/security/CVE-2020-35530
report https://ubuntu.com/security/CVE-2020-35531
report https://ubuntu.com/security/CVE-2020-35532
report https://ubuntu.com/security/CVE-2020-35533
report https://ubuntu.com/security/CVE-2021-32142
report https://ubuntu.com/security/CVE-2023-1729