# ALBA-2021:3056: nfs-utils bug fix and enhancement update

> NFS server fails to enforce sloppy mount option, potentially allowing unauthorized access or bypassing security restrictions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2021

## What is ALBA-2021:3056?

ALBA-2021:3056 is a vulnerability in libnfsidmap-devel, published on 10 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The nfs-utils packages provide a daemon for the kernel Network File System
(NFS) server and related tools, which provides better performance than the
traditional Linux NFS server used by most users. These packages also
contain the mount.nfs, umount.nfs, and showmount programs.

Bug Fix(es) and Enhancement(s):

* AlmaLinux 8.4 fails to obey sloppy mount option. (BZ#1982340)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libnfsidmap-devel` | AlmaLinux:8 | All versions | 1:2.3.3-41.el8_4.2 |

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

Apply the vendor's patch.

## Is ALBA-2021:3056 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2021:3056 is a vulnerability in libnfsidmap-devel, published on 10 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of ALBA-2021:3056 in the wild and no public exploit code.

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

## Sources

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

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