# ALBA-2021:1091: file bug fix and enhancement update

> The file utility update fixes ftype detection issues, ensuring accurate file type identification for system administrators and security tools.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Apr 2021

## What is ALBA-2021:1091?

ALBA-2021:1091 is a vulnerability in file-devel, published on 6 Apr 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The file command is used to identify a particular file according to the
type of data the file contains. It can identify many different file types,
including Executable and Linkable Format (ELF) binary files, system
libraries, RPM packages, and different graphics formats.

Bug Fix(es) and Enhancement(s):

* ftype detection is not working (BZ#1905906)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `file-devel` | AlmaLinux:8 | All versions | 5.33-16.el8_3.1 |

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

Apply the vendor's patch.

## Is ALBA-2021:1091 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2021:1091 is a vulnerability in file-devel, published on 6 Apr 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of ALBA-2021:1091 in the wild and no public exploit code.

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

## Sources

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

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