Vulnerability in radicale (CVE-2017-8342)
Summary
Vulnerability in radicale (CVE-2017-8342). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 190b1dd795f0c552a4992445a231da760211183b, 059ba8dec1f22ccbeab837e288b3833a099cee2d, 1.1.2 or later.
Original description
The description as published by the source.
Radicale before 1.1.2 and 2.x before 2.0.0rc2 is prone to timing oracles and simple brute-force attacks when using the htpasswd authentication method.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2017-8342 has been found in radicale.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: upgrade radicale to 190b1dd795f0c552a4992445a231da760211183b, 059ba8dec1f22ccbeab837e288b3833a099cee2d, 1.1.2 or later.
If unsure, ask your IT team or search "radicale CVE-2017-8342" on the vendor's site.
CVE-2017-8342 (radicale) — CWE-362 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 190b1dd795f0c552a4992445a231da760211183b, 059ba8dec1f22ccbeab837e288b3833a099cee2d, 1.1.2 — 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.
A vulnerability (CWE-362) exists in radicale.
Check the vendor advisory for the affected versions of radicale.
Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover.
Update to 190b1dd795f0c552a4992445a231da760211183b, 059ba8dec1f22ccbeab837e288b3833a099cee2d, 1.1.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'radicale' . 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 'radicale' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
radicaleを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade radicale to 190b1dd795f0c552a4992445a231da760211183b, 059ba8dec1f22ccbeab837e288b3833a099cee2d, 1.1.2ステージング環境で 190b1dd795f0c552a4992445a231da760211183b, 059ba8dec1f22ccbeab837e288b3833a099cee2d, 1.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2017-8342 radicale Fixed in: 1.1.1+20160115-4
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package pypi.org
- patch bugs.debian.org
- patch github.com
- patch github.com
- web lists.debian.org