Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2023-40587

Path Traversal in pyramid (CVE-2023-40587)

Summary

path traversal in pyramid (CVE-2023-40587). Risk of unauthorized operations or information disclosure. Exploitable via ``index.html``. Mitigation: upgrade to `2.0.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2023-40587** has been found in pyramid. Attackers can target a specific entry point like ``index.html`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade pyramid to **2.0.2** or later. If unsure, ask your IT team or search "pyramid CVE-2023-40587" on the vendor's site.
CVE-2023-40587 (pyramid) — CWE-22 / Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `index.html` / `os.path.normpath` Patched: `2.0.2` — apply immediately Workaround: Use a version of Python 3 that is not affected. 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
**Path traversal** (CWE-22) exists in pyramid. Attackers reach the vulnerable code path via ``index.html`` without authentication.
📍 Affected scope
pyramid — . Attack surface: `index.html` / `os.path.normpath`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.0.2**.
🛡️ Workaround
Workaround: Use a version of Python 3 that is not affected.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'pyramid' .` 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 'pyramid' . | grep -v node_modules

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

  2. 5
    Apply temporary workaround mitigate 
    Use a version of Python 3 that is not affected.

    パッチが適用されるまでの応急処置として、Use a version of Python 3 that is not affected. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch 
    Upgrade pyramid to 2.0.2

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

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

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

Affected packages

PyPI pyramid
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0"},{"fixed":"2.0.2"}]}]

References

🍪 About cookies

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

Details →