rpm package
suse/xrdp&distro=SUSE Linux Enterprise Server 12 SP2-LTSS
pkg:rpm/suse/xrdp&distro=SUSE%20Linux%20Enterprise%20Server%2012%20SP2-LTSS
Vulnerabilities (4)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2020-4044 | — | < 0.9.0~git.1456906198.f422461-16.20.1 | 0.9.0~git.1456906198.f422461-16.20.1 | Jun 30, 2020 | The xrdp-sesman service before version 0.9.13.1 can be crashed by connecting over port 3350 and supplying a malicious payload. Once the xrdp-sesman process is dead, an unprivileged attacker on the server could then proceed to start their own imposter sesman service listening on p | ||
| CVE-2017-16927 | Hig | 8.4 | < 0.9.0~git.1456906198.f422461-16.9.3 | 0.9.0~git.1456906198.f422461-16.9.3 | Nov 23, 2017 | The scp_v0s_accept function in sesman/libscp/libscp_v0.c in the session manager in xrdp through 0.9.4 uses an untrusted integer as a write length, which allows local users to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impa | |
| CVE-2017-6967 | Hig | 7.3 | < 0.9.0~git.1456906198.f422461-16.9.3 | 0.9.0~git.1456906198.f422461-16.9.3 | Mar 17, 2017 | xrdp 0.9.1 calls the PAM function auth_start_session() in an incorrect location, leading to PAM session modules not being properly initialized, with a potential consequence of incorrect configurations or elevation of privileges, aka a pam_limits.so bypass. | |
| CVE-2013-1430 | Cri | 9.8 | < 0.9.0~git.1456906198.f422461-16.9.3 | 0.9.0~git.1456906198.f422461-16.9.3 | Dec 16, 2016 | An issue was discovered in xrdp before 0.9.1. When successfully logging in using RDP into an xrdp session, the file ~/.vnc/sesman_${username}_passwd is created. Its content is the equivalent of the user's cleartext password, DES encrypted with a known key. |
- CVE-2020-4044Jun 30, 2020affected < 0.9.0~git.1456906198.f422461-16.20.1fixed 0.9.0~git.1456906198.f422461-16.20.1
The xrdp-sesman service before version 0.9.13.1 can be crashed by connecting over port 3350 and supplying a malicious payload. Once the xrdp-sesman process is dead, an unprivileged attacker on the server could then proceed to start their own imposter sesman service listening on p
- affected < 0.9.0~git.1456906198.f422461-16.9.3fixed 0.9.0~git.1456906198.f422461-16.9.3
The scp_v0s_accept function in sesman/libscp/libscp_v0.c in the session manager in xrdp through 0.9.4 uses an untrusted integer as a write length, which allows local users to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impa
- affected < 0.9.0~git.1456906198.f422461-16.9.3fixed 0.9.0~git.1456906198.f422461-16.9.3
xrdp 0.9.1 calls the PAM function auth_start_session() in an incorrect location, leading to PAM session modules not being properly initialized, with a potential consequence of incorrect configurations or elevation of privileges, aka a pam_limits.so bypass.
- affected < 0.9.0~git.1456906198.f422461-16.9.3fixed 0.9.0~git.1456906198.f422461-16.9.3
An issue was discovered in xrdp before 0.9.1. When successfully logging in using RDP into an xrdp session, the file ~/.vnc/sesman_${username}_passwd is created. Its content is the equivalent of the user's cleartext password, DES encrypted with a known key.