CVE-2017-6967

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.

These are all security issues fixed in the libpainter0-0.9.15-2.2 package on the GA media of openSUSE Tumbleweed.

This update for xrdp fixes the following issues:

These security issues were fixed:

• CVE-2013-1430: When successfully logging in using RDP into an xrdp session, the file ~/.vnc/sesman_${username}_passwd was created. Its content was the equivalent of the user's cleartext password, DES encrypted with a known key (bsc#1015567).
• CVE-2017-16927: The scp_v0s_accept function in sesman/libscp/libscp_v0.c in the session manager in xrdp through used an untrusted integer as a write length, which could lead to a local denial of service (bsc#1069591).
• CVE-2017-6967: Fixed call of the PAM function auth_start_session(). This lead to 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 (bsc#1029912).

These non-security issues were fixed:

• The KillDisconnected option for TigerVNC Xvnc sessions is now supported (bsc#1101506)
• Fixed an issue with delayed X KeyRelease events (bsc#1100453)
• Force xrdp-sesman.service to start after xrdp.service. (bsc#1014524)
• Avoid use of hard-coded sesman port. (bsc#1060644)
• Fixed a regression connecting from Windows 10. (bsc#1090174)

This update for xrdp fixes the following issues:

Security issues fixed:

• CVE-2013-1430: When successfully logging in using RDP into an xrdp session, the file ~/.vnc/sesman_${username}_passwd was created. Its content was the equivalent of the user's cleartext password, DES encrypted with a known key (bsc#1015567).
• CVE-2017-16927: The scp_v0s_accept function in sesman/libscp/libscp_v0.c in the session manager in xrdp through used an untrusted integer as a write length, which could lead to a local denial of service (bsc#1069591).
• CVE-2017-6967: Fixed call of the PAM function auth_start_session(). This lead to 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 (bsc#1029912).

Other issues addressed:

• The KillDisconnected option for TigerVNC Xvnc sessions is now supported (bsc#1101506)
• Fixed an issue with delayed X KeyRelease events (bsc#1100453)
• Force xrdp-sesman.service to start after xrdp.service. (bsc#1014524)
• Avoid use of hard-coded sesman port. (bsc#1060644)
• Backport upstream commit 5575197, sesman should stop setting LANG and let initialization scripts take care of it (bsc#1023988).
• Backport upstream patches for 32bpp support (bsc#1022098).
• Fixed a regression connecting from Windows 10. (bsc#1090174)

This update for xrdp provides the following fix:

• CVE-2020-4044: xrdp-sesman can be crashed remotely over port 3350 (bsc#1173580).
• Fixed an issue where xrdp-sesman could not restart (bsc#1155952).
• Fixed an issue where xrdp could not start due to an error in the service file use absolute path in ExecStart (bsc#1155789).
• Fixed a PAM error after 2nd xrdp session after logout (bsc#1153471).
• Fixed a crash in xrdp-sesman, caused by terminating and reconnecting an xrdp session (bsc#1152711).
• Fixed a failure in RDP session recovery (bsc#1150584).
• Fixed a process leak (bsc#1144379).
• Let systemd handle the daemons, fixing daemon start failures. (bsc#1138954, bsc#1144327)
• Don't try to create .vnc directory if it already exists. (bsc#1157860)

It was discovered that xrdp did not properly validate certain input in the session manager. A local attacker could possibly use this issue to cause a denial of service or other unspecified impact. (CVE-2017-16927)

It was discovered that xrdp did not properly initialize PAM session modules. A remote attacker could possibly use this issue to escalate privileges. (CVE-2017-6967)