← Back
CVE-2021-4286
Vulnerability in srp (CVE-2021-4286)
Summary
vulnerability in srp (CVE-2021-4286). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `dba52642f5e95d3da7af1780561213ee6053195f, 1.0.17` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2021-4286** has been found in srp.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade srp to **dba52642f5e95d3da7af1780561213ee6053195f, 1.0.17** or later.
If unsure, ask your IT team or search "srp CVE-2021-4286" on the vendor's site.
CVE-2021-4286 (srp) —
Patched: `dba52642f5e95d3da7af1780561213ee6053195f, 1.0.17` — 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 srp.
📍 Affected scope
srp — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **dba52642f5e95d3da7af1780561213ee6053195f, 1.0.17**.
🛡️ 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 '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
-
1Identify exposure identify
grep -r 'srp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `srp` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade srp to dba52642f5e95d3da7af1780561213ee6053195f, 1.0.17ステージング環境で dba52642f5e95d3da7af1780561213ee6053195f, 1.0.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
srp
[{"repo":"https:\/\/github.com\/cocagne\/pysrp","type":"GIT","events":[{"introduced":"0"},{"fixed":"dba52642f5e95d3da7af1780561213ee6053195f"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.17"}]}]
References
- advisory https://github.com/advisories/GHSA-xmc3-9m9j-w9x4
- patch https://github.com/cocagne/pysrp/commit/dba52642f5e95d3da7af1780561213ee6053195f
- web https://vuldb.com/?id.216875
- web https://vuldb.com/?ctiid.216875
- web https://github.com/cocagne/pysrp/releases/tag/1.0.17
- web https://github.com/cocagne/pysrp/pull/43