Fedora Project Sssd
By the Year
In 2022 there have been 0 vulnerabilities in Fedora Project Sssd . Sssd did not have any published security vulnerabilities last year.
Year | Vulnerabilities | Average Score |
---|---|---|
2022 | 0 | 0.00 |
2021 | 0 | 0.00 |
2020 | 0 | 0.00 |
2019 | 2 | 5.30 |
2018 | 2 | 6.50 |
It may take a day or so for new Sssd vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Fedora Project Sssd Security Vulnerabilities
A flaw was found in sssd Group Policy Objects implementation
CVE-2018-16838
5.4 - Medium
- March 25, 2019
A flaw was found in sssd Group Policy Objects implementation. When the GPO is not readable by SSSD due to a too strict permission settings on the server side, SSSD will allow all authenticated users to login instead of denying access.
Improper Privilege Management
A vulnerability was found in sssd
CVE-2019-3811
5.2 - Medium
- January 15, 2019
A vulnerability was found in sssd. If a user was configured with no home directory set, sssd would return '/' (the root directory) instead of '' (the empty string / no home directory). This could impact services that restrict the user's filesystem access to within their home directory through chroot() etc. All versions before 2.1 are vulnerable.
sssd versions from 1.13.0 to before 2.0.0 did not properly restrict access to the infopipe according to the "
CVE-2018-16883
5.5 - Medium
- December 19, 2018
sssd versions from 1.13.0 to before 2.0.0 did not properly restrict access to the infopipe according to the "allowed_uids" configuration parameter. If sensitive information were stored in the user directory, this could be inadvertently disclosed to local attackers.
Information Disclosure
The UNIX pipe which sudo uses to contact SSSD and read the available sudo rules from SSSD has too wide permissions, which means
CVE-2018-10852
7.5 - High
- June 26, 2018
The UNIX pipe which sudo uses to contact SSSD and read the available sudo rules from SSSD has too wide permissions, which means that anyone who can send a message using the same raw protocol that sudo and SSSD use can read the sudo rules available for any user. This affects versions of SSSD before 1.16.3.
Information Disclosure
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Canonical Ubuntu Linux or by Fedora Project? Click the Watch button to subscribe.
