Skip to content

xrdp allows an ininite number of login attempts

High
metalefty published GHSA-7w22-h4w7-8j5j Jul 12, 2024

Package

xrdp

Affected versions

<= 0.9.26

Patched versions

0.10.0

Description

Summary

The MaxLoginRetry parameter in /etc/xrdp/sesman.ini is effectively broken in xrdp. Attackers can make an infinite number of login attempts.

Details

xrdp versions prior to 0.10.0 have a vulnerability that allows attackers to make an infinite number of login attempts. The number of max login attempts is supposed to be limited by a configuration parameter MaxLoginRetry in /etc/xrdp/sesman.ini. However, this mechanism was not effectively working. As a result, xrdp allows an infinite number of login attempts.

The issue is fixed at xrdp 0.10.0 or later however xrdp 0.9.x is reaching EoL and no fixes are currently planned. Users are recommended to update xrdp to 0.10.0.

If you have difficulty updating to 0.10.0, restrict access to xrdp at the network layer using a firewall not expose xrdp to untrusted clients. Also, consider using other security measures such as pam_faillock(8).

References

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
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
Low

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:L/PR:N/UI:N/S:C/C:L/I:N/A:L

CVE ID

CVE-2024-39917

Weaknesses

No CWEs

Credits