# ALBA-2022:2147: sssd bug fix and enhancement update

> A bug in SSSD causes the NSS responder to exit and restart in a loop, leading to a denial of service for authentication services.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 May 2022

## What is ALBA-2022:2147?

ALBA-2022:2147 is a denial of service vulnerability in libipa_hbac, published on 10 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### 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):

* sssd_nss exiting (due to missing 'sssd' local user) making SSSD service to restart in a loop (BZ#2074648)

## Which versions are affected by ALBA-2022:2147?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libipa_hbac` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `libsss_autofs` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `libsss_certmap` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `libsss_idmap` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `libsss_nss_idmap` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `libsss_nss_idmap-devel` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `libsss_simpleifp` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `libsss_sudo` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `python3-libipa_hbac` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `python3-libsss_nss_idmap` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `python3-sss` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `python3-sss-murmur` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `python3-sssdconfig` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-ad` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-client` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-common` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-common-pac` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-dbus` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-ipa` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-kcm` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-krb5` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-krb5-common` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-ldap` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-nfs-idmap` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-polkit-rules` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-proxy` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-tools` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |
| `sssd-winbind-idmap` | AlmaLinux:8 | All versions | 2.6.2-4.el8_6 |

## How do I fix ALBA-2022:2147?

Apply the vendor's patch.

## Is ALBA-2022:2147 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2022:2147 is a denial of service vulnerability in libipa_hbac, published on 10 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of ALBA-2022:2147 in the wild and no public exploit code.

Affected product: libipa_hbac. 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-2022-2147/ (Markdown: https://insights.sbomify.com/ALBA-2022-2147/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2022:2147

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