CVE-2021-41617

Description

sshd in OpenSSH 6.2 through 8.x before 8.8, when certain non-default configurations are used, allows privilege escalation because supplemental groups are not initialized as expected. Helper programs for AuthorizedKeysCommand and AuthorizedPrincipalsCommand may run with privileges associated with group memberships of the sshd process, if the configuration specifies running the command as a different user.

7.0

CVSS

Severity: High

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.28%

Vendor Advisory fedoraproject.org Vendor Advisory fedoraproject.org Vendor Advisory fedoraproject.org Vendor Advisory debian.org Vendor Advisory openssh.com Vendor Advisory openssh.com

Affected: n/a n/a

References

Link	Tags
https://www.openssh.com/security.html	vendor advisory
https://www.openwall.com/lists/oss-security/2021/09/26/1	third party advisory mailing list
https://www.openssh.com/txt/release-8.8	release notes vendor advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6XJIONMHMKZDTMH6BQR5TNLF2WDCGWED/	vendor advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/W44V2PFQH5YLRN6ZJTVRKAD7CU6CYYET/	vendor advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KVI7RWM2JLNMWTOFK6BDUSGNOIPZYPUT/	vendor advisory
https://www.oracle.com/security-alerts/cpuapr2022.html	third party advisory patch
https://bugzilla.suse.com/show_bug.cgi?id=1190975	issue tracking third party advisory patch
https://security.netapp.com/advisory/ntap-20211014-0004/	third party advisory
https://www.oracle.com/security-alerts/cpujul2022.html	third party advisory
https://www.starwindsoftware.com/security/sw-20220805-0001/	third party advisory
https://www.tenable.com/plugins/nessus/154174
https://www.debian.org/security/2023/dsa-5586	vendor advisory
https://lists.debian.org/debian-lts-announce/2023/12/msg00017.html	mailing list

Frequently Asked Questions

What is the severity of CVE-2021-41617?: CVE-2021-41617 has been scored as a high severity vulnerability.
How to fix CVE-2021-41617?: To fix CVE-2021-41617, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2021-41617 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2021-41617 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.