Vulnerability in eve-srp (CVE-2020-36660)

Summary

vulnerability in eve-srp (CVE-2020-36660). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `9e03f68e46e85ca9c9694a6971859b3ee66f0240` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2020-36660** has been found in eve-srp. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade eve-srp to **9e03f68e46e85ca9c9694a6971859b3ee66f0240** or later. If unsure, ask your IT team or search "eve-srp CVE-2020-36660" on the vendor's site.

CVE-2020-36660 (eve-srp) — Attack vector: remote (network-reachable) / no user interaction Patched: `9e03f68e46e85ca9c9694a6971859b3ee66f0240` — 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 eve-srp.

📍 Affected scope

eve-srp — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **9e03f68e46e85ca9c9694a6971859b3ee66f0240**.

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

Affected packages

PyPI eve-srp

[{"repo":"https:\/\/github.com\/paxswill\/evesrp","type":"GIT","events":[{"introduced":"0"},{"fixed":"9e03f68e46e85ca9c9694a6971859b3ee66f0240"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]