CVE-2017-8342 json
Radicale is vulnerable to timing oracles and simple bruteforce attacks
published 2017-04-30 9 y ago modified 2026-06-17 4 mo ago also GHSA-rpv4-63g3-9x23 , PYSEC-2017-102 , EUVD-2017-0110
- cvss
- 8.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi radicale 1.1.2, 2.0.0rc2
- radicale Debian 14, Debian 13, Debian 12 1.1.1+20160115-4
debian advisories DEBIAN-CVE-2017-8342
- github.com/Kozea/Radicale@059ba8d commit
- github.com/Kozea/Radicale@190b1dd commit
- bugs.debian.org/861514 patch
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-8342 updated cvss 5.9
radicale: Insufficient protection against timing oracles and bruteforce attacks
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.02% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugs.debian.org https://bugs.debian.org/861514 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | radicale | <1.1.2 >=2.0.0rc1, <2.0.0rc2 |
1.1.2 2.0.0rc2 |
Classification
- Weakness
-
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
References
-
github.com
/Kozea/Radicale/commit/059ba8dec1f22ccbeab837e288b3833a099cee2d
web, patch, third-party-advisory
-
github.com
/Kozea/Radicale/commit/190b1dd795f0c552a4992445a231da760211183b
web, patch, third-party-advisory
-
bugs.debian.org
/861514
web, exploit, issue-tracking, patch, vdb-entry
-
github.com
/Kozea/Radicale/blob/1.1.2/NEWS.rst
web, release-notes, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2020/04/msg00019.html
mailing-list, web
-
nvd.nist.gov
/vuln/detail/CVE-2017-8342
advisory
-
github.com
/Kozea/Radicale
package
-
github.com
/pypa/advisory-database/tree/main/vulns/radicale/PYSEC-2017-102.yaml
web
-
pypi.org
/project/radicale
package
-
github.com
/advisories/GHSA-rpv4-63g3-9x23
advisory
Sources
- CVE List CVE-2017-8342
- GitHub Advisory GHSA-rpv4-63g3-9x23
- NVD CVE-2017-8342
- OSV PYSEC-2017-102
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.