Skip to content

Radicale is vulnerable to timing oracles and simple bruteforce attacks

High severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Oct 16, 2024

Package

pip Radicale (pip)

Affected versions

< 1.1.2
= 2.0.0rc1

Patched versions

1.1.2
2.0.0rc2

Description

Radicale before 1.1.2 and 2.0.0rc1 is prone to timing oracles and simple brute-force attacks when using the htpasswd authentication method.

References

Published by the National Vulnerability Database Apr 30, 2017
Published to the GitHub Advisory Database May 13, 2022
Reviewed Aug 4, 2023
Last updated Oct 16, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.360%
(73rd percentile)

Weaknesses

CVE ID

CVE-2017-8342

GHSA ID

GHSA-rpv4-63g3-9x23

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.