← Back
CVE-2017-8342
high
CVSS 8.1
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-362) exists in radicale.
📍 Affected scope
radicale — .
🔥 Severity
Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **190b1dd795f0c552a4992445a231da760211183b, 059ba8dec1f22ccbeab837e288b3833a099cee2d, 1.1.2**.
🛡️ 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 'radicale' .` 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 'radicale' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `radicale` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade radicale to 190b1dd795f0c552a4992445a231da760211183b, 059ba8dec1f22ccbeab837e288b3833a099cee2d, 1.1.2ステージング環境で 190b1dd795f0c552a4992445a231da760211183b, 059ba8dec1f22ccbeab837e288b3833a099cee2d, 1.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
radicale
[{"repo":"https:\/\/github.com\/Kozea\/Radicale","type":"GIT","events":[{"introduced":"0"},{"fixed":"190b1dd795f0c552a4992445a231da760211183b"},{"fixed":"059ba8dec1f22ccbeab837e288b3833a099cee2d"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2017-8342
- advisory https://github.com/advisories/GHSA-rpv4-63g3-9x23
- package https://pypi.org/project/radicale
- patch https://github.com/Kozea/Radicale/commit/059ba8dec1f22ccbeab837e288b3833a099cee2d
- patch https://github.com/Kozea/Radicale/commit/190b1dd795f0c552a4992445a231da760211183b
- web https://bugs.debian.org/861514
- web https://github.com/Kozea/Radicale/blob/1.1.2/NEWS.rst
- web https://lists.debian.org/debian-lts-announce/2020/04/msg00019.html