# ALBA-2021:2571: sssd bug fix and enhancement update

> SSSD update fixes bugs including a security bypass where implicit deny policies failed to block logins.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 29 Jun 2021

## What is ALBA-2021:2571?

ALBA-2021:2571 is a vulnerability in libsss_nss_idmap-devel, published on 29 Jun 2021. 

### Official description

The System Security Services Daemon (SSSD) service provides a set of
daemons to manage access to remote directories and authentication
mechanisms. It also provides the Name Service Switch (NSS) and the
Pluggable Authentication Modules (PAM) interfaces toward the system, and a
pluggable back-end system to connect to multiple different account sources.

Bug Fix(es) and Enhancement(s):

* Wrong default debug level of sssd tools (BZ#1942438)

* IPA missing secondary IPA Posix groups in latest sssd 1.16.5-10.el7_9.7
(BZ#1945654)

* SSSD  not detecting subdomain from AD forest (AlmaLinux 8.3) (BZ#1945655)

* No gpo found and ad_gpo_implicit_deny set to True still permits user
login (BZ#1945656)

* pam_sss_gss.so doesn't work with large kerberos tickets (BZ#1949170)

## Which versions are affected by ALBA-2021:2571?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libsss_nss_idmap-devel` | AlmaLinux:8 | All versions | 2.4.0-9.el8_4.1 |

## How do I fix ALBA-2021:2571?

Apply the vendor's patch.

## Is ALBA-2021:2571 being exploited?

There is no known exploitation of ALBA-2021:2571 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALBA-2021:2571 and fix it if it is affected.

What it is: ALBA-2021:2571 is a vulnerability in libsss_nss_idmap-devel, published on 29 Jun 2021. 
Exploitation: There is no known exploitation of ALBA-2021:2571 in the wild and no public exploit code.

Affected product: libsss_nss_idmap-devel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/ALBA-2021-2571/ (Markdown: https://insights.sbomify.com/ALBA-2021-2571/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2021:2571

---
From sbomify Insights: https://insights.sbomify.com/ALBA-2021-2571/
Summaries are generated and may contain mistakes; the official description above is the record.