← Back
CVE-2024-28865

Vulnerability in wiki (CVE-2024-28865)

Summary

vulnerability in wiki (CVE-2024-28865). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.10.1` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2024-28865** has been found in wiki. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade wiki to **0.10.1** or later. If unsure, ask your IT team or search "wiki CVE-2024-28865" on the vendor's site.
CVE-2024-28865 (wiki) — CWE-1333 / Attack vector: remote (network-reachable) / unauthenticated / no user interaction Patched: `0.10.1` — apply immediately Workaround: Close off access to create and edit articles by anonymous users. 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** (CWE-1333) exists in wiki.
📍 Affected scope
wiki — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.10.1**.
🛡️ Workaround
Workaround: Close off access to create and edit articles by anonymous users.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'wiki' .` 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. 1
    Identify exposure identify
    grep -r 'wiki' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `wiki` を grep し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply temporary workaround mitigate
    Close off access to create and edit articles by anonymous users.

    パッチが適用されるまでの応急処置として、Close off access to create and edit articles by anonymous users. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch
    Upgrade wiki to 0.10.1

    ステージング環境で 0.10.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI wiki
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.10.1"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →