On this page (7 sections)

Ubuntu has published USN-9084-1, a security notice for Radicale, the lightweight calendar and addressbook (CalDAV/CardDAV) server. The flaw is that Radicale did not slow down failed login attempts when it used htpasswd authentication, which makes password guessing easier for a remote attacker.

If you run Radicale on Ubuntu 16.04 LTS with Extended Security Maintenance (ESM) and expose it to a network, you should update and restart the service. The notice is the only source for this story so far, so some details below are marked as not stated.

What happened

Ubuntu's notice says Radicale did not delay failed authentication attempts when using htpasswd authentication. Ubuntu summarizes the impact as exposure of sensitive information over the network: a remote attacker could possibly obtain user passwords through timing or brute-force attacks. The wording is cautious ("could possibly"), and the notice gives no further technical detail.

The notice references CVE-2017-8342. The research available for this story did not include the CVE record itself, so we do not state a CVSS score or any details beyond what Ubuntu wrote.

Why a missing delay matters

Password checks are only as strong as the number of guesses an attacker can make. When a server answers a wrong password immediately, every attempt costs the attacker almost nothing, so automated guessing can run fast. A small delay after each failure, or a lockout, makes that approach much slower and easier to notice.

The notice also mentions timing attacks. In general terms, that means measuring how long the server takes to respond and using differences to learn something about the credentials. Ubuntu does not describe how this applies to Radicale, so treat the timing aspect as a general caution rather than a confirmed method.

Who is affected

  • Systems running Ubuntu 16.04 LTS with the Radicale packages from the ESM archive. The fixed packages in the notice are listed only for that release.
  • Radicale instances configured for htpasswd authentication. The notice describes the issue in that context only.
  • Servers reachable from the internet or other untrusted networks, where a remote attacker can send repeated login attempts.
  • Setups with weak or reused passwords, since guessing succeeds sooner against them.

The notice does not say whether other Ubuntu releases or other distributions are affected. If you run Radicale elsewhere, check your own vendor's advisories.

How to check your exposure

This read-only command lists the installed Radicale packages and their versions on Debian-based systems such as Ubuntu. On Ubuntu 16.04 LTS you are looking for 1.1.1-1ubuntu0.1~esm1 or later.

List installed Radicale packages and versions (Ubuntu/Debian)Shell
dpkg -l | grep -i radicale

Next, confirm how authentication is configured. Radicale's configuration file location depends on how it was installed, so check your own setup. Look for the authentication type in the configuration and see whether it is set to htpasswd.

What to do now

Caution. Updating Radicale requires restarting the service, which briefly interrupts calendar and contact sync for your users. Do it in a quiet window.
  1. Confirm you run Ubuntu 16.04 LTS with ESM and that the Radicale packages are installed.
  2. Run a standard system update so the radicale, python-radicale and python3-radicale packages reach 1.1.1-1ubuntu0.1~esm1 or later.
  3. Restart Radicale after the update, as the notice instructs, so the fix takes effect.
  4. Re-run the version check to confirm the new package version is installed.
  5. Review whether Radicale needs to be reachable from the internet. If not, restrict it to a VPN or internal network.
  6. Change passwords for Radicale users if you see signs of repeated failed logins, and require strong, unique passwords going forward.

The first block below updates only the Radicale packages on Ubuntu 16.04 LTS; afterwards, re-run the version check and look for 1.1.1-1ubuntu0.1~esm1 or later.

Update only the Radicale packages (Ubuntu 16.04 LTS with ESM)Shell
sudo apt-get update
sudo apt-get install --only-upgrade radicale python-radicale python3-radicale

This command restarts the service so the fix takes effect. The service name can differ by installation, so confirm it on your system before restarting.

Restart Radicale after updating (systemd-based systems)Shell
sudo systemctl restart radicale
Tip. The fixed packages carry an ESM version suffix (esm1). If the update does not appear, check that your machine has access to the ESM archive. Ubuntu's notice says Ubuntu Pro provides ten-year security coverage for 25,000+ packages and is free for up to five machines.

Detection and monitoring

Even after patching, watch for password guessing against any login you expose. Review your reverse proxy or web server access logs for many failed authentication responses (HTTP 401) from the same address in a short time, and for logins that succeed right after a long run of failures.

A rate limit or firewall rule in front of Radicale adds a second layer, which matters because a delay alone does not stop a patient attacker. Our guide on what a WAF is explains how that kind of control works, and Webforta Monitor can alert you to uptime, certificate and DNS changes on the public hostname that serves your calendar.

For broader context on keeping small servers tidy, see website security for small business.

What we do not know

  • No CVSS score or severity rating is given in the notice.
  • The notice does not say whether the flaw has been exploited in the wild.
  • It does not describe how a timing attack would work against Radicale.
  • It lists fixed packages only for Ubuntu 16.04 LTS.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. USN-9084-1: Radicale vulnerability | Ubuntu security notices | Ubuntuubuntu.com ·
  • Radicale
  • Ubuntu
  • USN
  • brute force
  • authentication