CVE-2019-3811
published 2019-01-15CVE-2019-3811: 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…
PriorityP421medium5.2CVSS 3.1
AVAACLPRLUIRSUCNINAH
EPSS
0.70%
49.0th percentile
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.
Affected
13 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | sssd | < sssd 2.2.0-1 (bookworm) | sssd 2.2.0-1 (bookworm) |
| fedoraproject | sssd | < 2.1 | 2.1 |
| fedoraproject | sssd | >= 0 < 2.2.0-1 | 2.2.0-1 |
| fedoraproject | sssd | >= 0 < 2.2.0-1 | 2.2.0-1 |
| fedoraproject | sssd | >= 0 < 2.2.0-1 | 2.2.0-1 |
| fedoraproject | sssd | >= 0 < 2.2.0-1 | 2.2.0-1 |
| fedoraproject | sssd | >= 0 < 1.16.1-1ubuntu1.8 | 1.16.1-1ubuntu1.8 |
| fedoraproject | sssd | >= 0 < 2.2.3-3ubuntu0.7 | 2.2.3-3ubuntu0.7 |
| opensuse | leap | — | — |
| opensuse | leap | — | — |
| redhat | enterprise_linux | — | — |
| the_sssd_project | sssd | — | — |
CVSS provenance
nvdv3.15.2MEDIUMCVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H
nvdv3.04.1MEDIUMCVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
nvdv2.02.7LOWAV:A/AC:L/Au:S/C:N/I:N/A:P
osv7.5HIGH
vendor_debian5.2MEDIUM
vendor_redhat5.2MEDIUM
vendor_ubuntu3.8LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
SSSD vulnerabilities
vendor_ubuntu·2021-09-08·CVSS 3.8
CVE-2021-3621 [LOW] SSSD vulnerabilities
Title: SSSD vulnerabilities
Summary: Several security issues were fixed in sssd.
Jakub Hrozek discovered that SSSD incorrectly handled file permissions. A
local attacker could possibly use this issue to read the sudo rules
available for any user. This issue only affected Ubuntu 18.04 LTS.
(CVE-2018-10852)
It was discovered that SSSD incorrectly handled Group Policy Objects. When
SSSD is configured with too strict permissions causing the GPO to not be
readable, SSSD will allow all authenticated users to login instead of being
denied, contrary to expectations. This issue only affected Ubuntu 18.04
LTS. (CVE-2018-16838)
It was discovered that SSSD incorrectly handled users with no home
directory set. When no home directory was set, SSSD would return the root
directory instead of an empty
Debian
CVE-2019-3811: sssd - A vulnerability was found in sssd. If a user was configured with no home directo...
vendor_debian·2019·CVSS 5.2
CVE-2019-3811 [MEDIUM] CVE-2019-3811: sssd - A vulnerability was found in sssd. If a user was configured with no home directo...
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.
Scope: local
bookworm: resolved (fixed in 2.2.0-1)
bullseye: resolved (fixed in 2.2.0-1)
forky: resolved (fixed in 2.2.0-1)
sid: resolved (fixed in 2.2.0-1)
trixie: resolved (fixed in 2.2.0-1)
Red Hat
sssd: fallback_homedir returns '/' for empty home directories in passwd file
vendor_redhat·2018-12-04·CVSS 5.2
CVE-2019-3811 [MEDIUM] CWE-552 sssd: fallback_homedir returns '/' for empty home directories in passwd file
sssd: fallback_homedir returns '/' for empty home directories in passwd file
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.
A vulnerability was found in sssd where, 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().
Package: sssd (Red Hat Enterprise Linux 6) - Will not fix
Pac
GHSA
GHSA-x3cx-wjrx-m7rj: A vulnerability was found in sssd
ghsa_unreviewed·2022-05-13
CVE-2019-3811 [MEDIUM] CWE-200 GHSA-x3cx-wjrx-m7rj: A vulnerability was found in sssd
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.
OSV
sssd vulnerabilities
osv·2021-09-08·CVSS 7.5
CVE-2018-10852 [HIGH] sssd vulnerabilities
sssd vulnerabilities
Jakub Hrozek discovered that SSSD incorrectly handled file permissions. A
local attacker could possibly use this issue to read the sudo rules
available for any user. This issue only affected Ubuntu 18.04 LTS.
(CVE-2018-10852)
It was discovered that SSSD incorrectly handled Group Policy Objects. When
SSSD is configured with too strict permissions causing the GPO to not be
readable, SSSD will allow all authenticated users to login instead of being
denied, contrary to expectations. This issue only affected Ubuntu 18.04
LTS. (CVE-2018-16838)
It was discovered that SSSD incorrectly handled users with no home
directory set. When no home directory was set, SSSD would return the root
directory instead of an empty string, possibly bypassing security measures.
This issue only
OSV
CVE-2019-3811: A vulnerability was found in sssd
osv·2019-01-15·CVSS 5.2
CVE-2019-3811 [MEDIUM] CVE-2019-3811: A vulnerability was found in sssd
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-3811 sssd: fallback_homedir returns '/' for empty home directories in passwd file
bugzilla·2018-12-05·CVSS 5.2
CVE-2019-3811 [MEDIUM] CVE-2019-3811 sssd: fallback_homedir returns '/' for empty home directories in passwd file
CVE-2019-3811 sssd: fallback_homedir returns '/' for empty home directories in passwd file
An issue was found in SSSD. The default option for fallback_homedir returns '/' for empty home directories in the passwd file.
References:
https://github.com/SSSD/sssd/pull/703
Upstream Patch:
https://github.com/SSSD/sssd/pull/703/commits/fa0a6400ebd2f4056a057914355ec2ddefc14fe6
https://github.com/SSSD/sssd/pull/703/commits/fe11bd0d5b7dea9f1723c5a59ba0c47641802797
Discussion:
Created sssd tracking bugs for this issue:
Affects: fedora-all [bug 1656619]
---
Introduced in:
https://github.com/SSSD/sssd/commit/704cc1c7
---
Further upstream patch:
https://github.com/SSSD/sssd/commit/90f32399b4
This addresses another part of the flaw that was introduced prior to the part linked on comment 2. S
Bugzilla
CVE-2019-3811 sssd: fallback_homedir returns '/' for empty home directories in passwd file [fedora-all]
bugzilla·2018-12-05·CVSS 5.2
CVE-2019-3811 [MEDIUM] CVE-2019-3811 sssd: fallback_homedir returns '/' for empty home directories in passwd file [fedora-all]
CVE-2019-3811 sssd: fallback_homedir returns '/' for empty home directories in passwd file [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects m
http://lists.opensuse.org/opensuse-security-announce/2019-03/msg00026.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-04/msg00045.htmlhttp://www.securityfocus.com/bid/106644https://access.redhat.com/errata/RHSA-2019:2177https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3811https://lists.debian.org/debian-lts-announce/2019/01/msg00011.htmlhttps://lists.debian.org/debian-lts-announce/2023/05/msg00028.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-03/msg00026.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-04/msg00045.htmlhttp://www.securityfocus.com/bid/106644https://access.redhat.com/errata/RHSA-2019:2177https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3811https://lists.debian.org/debian-lts-announce/2019/01/msg00011.htmlhttps://lists.debian.org/debian-lts-announce/2023/05/msg00028.html
2019-01-15
Published