NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2017-8342 — radicale

HIGHFix: Kozea/Radicale@059ba8d

CVE-2017-8342 is a high-severity (CVSS 8.1) CWE-362 vulnerability in radicale. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for radicale — see the affected versions and patch details below.

Radicale is vulnerable to timing oracles and simple bruteforce attacks

Also known asGHSA-rpv4-63g3-9x23PYSEC-2017-102
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk
0.00%0.84%1.69%2.53%0.7%2.0%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐍radicale🐍radicale

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIradicaleall versions1.1.2pip install --upgrade 'radicale==1.1.2'
🐍PyPIradicale≥ 2.0.0rc1&&< 2.0.0rc22.0.0rc2pip install --upgrade 'radicale==2.0.0rc2'

Affected Products

1 product · 2 configurations
Application
radicaleradicale
≤ 1.1.1
1 version
2.0.0
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Radicale before 1.1.2 and 2.x before 2.0.0rc2 is prone to timing oracles…

bugs.debian.orgNVDApr 2020

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for radicale, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update radicale to 1.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-8342 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2017-8342 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2017-8342: radicale — Fixed in 1.1.2