← Back
USN-4478-2
Vulnerability in python-rsa (USN-4478-2)
Summary
vulnerability in python-rsa (USN-4478-2). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `3.2.3-1.1ubuntu0.1~esm1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **USN-4478-2** has been found in python-rsa.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade python-rsa to **3.2.3-1.1ubuntu0.1~esm1** or later.
If unsure, ask your IT team or search "python-rsa USN-4478-2" on the vendor's site.
USN-4478-2 (python-rsa) —
Patched: `3.2.3-1.1ubuntu0.1~esm1` — 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 python-rsa.
📍 Affected scope
python-rsa — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.2.3-1.1ubuntu0.1~esm1**.
🛡️ 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 'python-rsa' .` 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 'python-rsa' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `python-rsa` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade python-rsa to 3.2.3-1.1ubuntu0.1~esm1ステージング環境で 3.2.3-1.1ubuntu0.1~esm1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:16.04:LTS
python-rsa
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-1.1ubuntu0.1~esm1"}]}]
Ubuntu:Pro:18.04:LTS
python-rsa
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.2-1ubuntu0.1~esm1"}]}]
Ubuntu:Pro:20.04:LTS
python-rsa
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0-3ubuntu0.1~esm1"}]}]