# ALBA-2021:3055: NetworkManager bug fix and enhancement update

> An attacker can cause incorrect hostname setting via IPv6 DNS reverse lookup, potentially leading to information disclosure in AlmaLinux systems.

- **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:3055?

ALBA-2021:3055 is a vulnerability in NetworkManager-libnm-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

NetworkManager is a system network service that manages network devices and
connections, attempting to keep active network connectivity when available.
Its capabilities include managing Ethernet, wireless, mobile broadband
(WWAN), and PPPoE devices, as well as providing VPN integration with a
variety of different VPN services.

Bug Fix(es) and Enhancement(s):

* Incorrect set hostname to localhost using DNS reverse lookup of ipv6
address (BZ#1970398)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `NetworkManager-libnm-devel` | AlmaLinux:8 | All versions | 1:1.30.0-10.el8_4 |

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

Apply the vendor's patch.

## Is ALBA-2021:3055 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2021:3055 is a vulnerability in NetworkManager-libnm-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:3055 in the wild and no public exploit code.

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

## Sources

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

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