← Back
CVE-2024-37155
Vulnerability in pycti (CVE-2024-37155)
Summary
vulnerability in pycti (CVE-2024-37155). Risk of unauthorized operations or information disclosure. Exploitable via ``secureIntrospectionPlugin``. Mitigation: upgrade to `6.1.9` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-37155** has been found in pycti.
Attackers can target a specific entry point like ``secureIntrospectionPlugin`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade pycti to **6.1.9** or later.
If unsure, ask your IT team or search "pycti CVE-2024-37155" on the vendor's site.
CVE-2024-37155 (pycti) — CWE-284 /
Attack surface: `secureIntrospectionPlugin`
Patched: `6.1.9` — 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** (CWE-284) exists in pycti. Attackers reach the vulnerable code path via ``secureIntrospectionPlugin`` without authentication.
📍 Affected scope
pycti — . Attack surface: `secureIntrospectionPlugin`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.1.9**.
🛡️ 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 'pycti' .` 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
-
1Identify exposure identify
grep -r 'pycti' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pycti` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pycti to 6.1.9ステージング環境で 6.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
pycti
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.9"}]}]
References
- web https://github.com/OpenCTI-Platform/opencti/security/advisories/GHSA-4mvw-j8r9-xcgc
- web https://nvd.nist.gov/vuln/detail/CVE-2024-37155
- web https://github.com/OpenCTI-Platform/opencti/commit/f87d96918c63b0c3d3ebfbea6c789d48e2f56ad5
- web https://github.com/OpenCTI-Platform/opencti/blob/6343b82b0b0a5d3ded3b30d08ce282328a556268/opencti-platform/opencti-graphql/src/graphql/graphql.js#L83-L94
- web https://github.com/pypa/advisory-database/tree/main/vulns/pycti/PYSEC-2024-313.yaml
- web https://github.com/advisories/GHSA-4mvw-j8r9-xcgc