Vulnerability in ether/logs (CVE-2021-32752)
Summary
Vulnerability in ether/logs (CVE-2021-32752). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.0.4 or later.
Original description
The description as published by the source.
Impact
A vulnerability was found that allowed authenticated admin users to access any file on the server.
Patches
The vulnerability has been fixed in 3.0.4.
Workarounds
We recommend disabling the plugin if untrustworthy sources have admin access.
For more information
If you have any questions or comments about this advisory:
- Open an issue in ether/logs
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-32752 has been found in ether/logs.
Successful exploitation can lead to full system takeover.
What to do: upgrade ether/logs to 3.0.4 or later.
If unsure, ask your IT team or search "ether/logs CVE-2021-32752" on the vendor's site.
CVE-2021-32752 (ether/logs) — CWE-552
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.0.4 — apply immediately
Workaround: We recommend disabling the plugin if untrustworthy sources have admin access.
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.
A vulnerability (CWE-552) exists in ether/logs.
Check the vendor advisory for the affected versions of ether/logs.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 3.0.4.
Workaround: We recommend disabling the plugin if untrustworthy sources have admin access.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ether/logs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ether/logs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ether/logsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
We recommend disabling the plugin if untrustworthy sources have admin access.パッチが適用されるまでの応急処置として、We recommend disabling the plugin if untrustworthy sources have admin access. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade ether/logs to 3.0.4ステージング環境で 3.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com