CVE-2017-8342: Radicale before 1.1.2 and 2.x before 2.0.0rc2 is prone to timing oracles and simple brute-force attacks when u

Q: How do I fix CVE-2017-8342?

radicale: upgrade to newer than 1.1.1. Exact commands for each OS are on this page.

Q: Is CVE-2017-8342 being exploited?

CVE-2017-8342 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-8342 affect?

CVE-2017-8342 affects radicale. Severity is high (CVSS 8.1). 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.

Q: How urgent is CVE-2017-8342?

Priority 59/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 8.1REMOTEUPGRADE

CVE-2017-8342 is a high-severity flaw (CVSS 8.1) affecting radicale. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	2.0% (top 19%)
CISA exploited list	No
Weakness	CWE-362
Published	2017-04-30
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: radicale

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-04-30 15:59 UTCPublished CVE record published
2026-06-17 01:26 UTCUpdated Record last modified

radicale radicale UPGRADE

Affected: <= 1.1.1 · 2.0.0 rc1

Fixed in: newer than 1.1.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy radicale || rpm -q radicale || radicale --version

2. UPGRADE to newer than 1.1.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade radicale

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade radicale

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-8342?

radicale: upgrade to newer than 1.1.1. Exact commands for each OS are on this page.

Is CVE-2017-8342 being exploited?

CVE-2017-8342 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-8342 affect?

CVE-2017-8342 affects radicale. Severity is high (CVSS 8.1). 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.

How urgent is CVE-2017-8342?

Priority 59/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2016-1505 CRITICAL 10.0 UPGRADE The filesystem storage backend in Radicale before 1.1 on Windows allows remote attackers to read or write to a
CVE-2015-8748 MEDIUM 5.3 UPGRADE Radicale before 1.1 allows remote authenticated users to bypass owner_write and owner_only limitations via reg
CVE-2015-8747 CRITICAL 10.0 UPGRADE The multifilesystem storage backend in Radicale before 1.1 allows remote attackers to read or write to arbitra

References

← Back to latest CVEs