# ALBA-2019:1970: authd bug fix update


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 30 Jul 2019

## What is ALBA-2019:1970?

ALBA-2019:1970 is a vulnerability in authd, published on 30 Jul 2019. 

### Official description

The authd packages contain authd, a small and fast RFC 1413 ident protocol
daemon with both xinetd server and interactive modes that supports IPv6 and IPv4 as well as the more popular features of pidentd.

Bug Fix(es):

* authd authentication fails with ERROR:NO-USER (BZ#1730802)

Users of authd are advised to upgrade to this updated package, which fixes this bug.

## Which versions are affected by ALBA-2019:1970?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `authd` | AlmaLinux:8 | All versions | 1.4.4-5.el8_0.1 |

## How do I fix ALBA-2019:1970?

Upgrade to a fixed version.

## Is ALBA-2019:1970 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2019:1970 is a vulnerability in authd, published on 30 Jul 2019. 
Exploitation: There is no known exploitation of ALBA-2019:1970 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2019:1970

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