# ALEA-2020:1691: libva bug fix and enhancement update

> An unspecified flaw in the libva video library affects AlmaLinux systems; users should apply the update.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** Yes
- **Published:** 28 Apr 2020

## What is ALEA-2020:1691?

ALEA-2020:1691 is an other vulnerability in libva, published on 28 Apr 2020. 

### Official description

For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.

## Which versions are affected by ALEA-2020:1691?

An affected version is exposed as installed. No special setting or call is needed.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libva` | AlmaLinux:8 | All versions | 2.5.0-2.el8 |
| `libva-devel` | AlmaLinux:8 | All versions | 2.5.0-2.el8 |

## How do I fix ALEA-2020:1691?

Upgrade to a fixed version.

## Is ALEA-2020:1691 being exploited?

There is no known exploitation of ALEA-2020:1691 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALEA-2020:1691 and fix it if it is affected.

What it is: ALEA-2020:1691 is an other vulnerability in libva, published on 28 Apr 2020. 
Exploitation: There is no known exploitation of ALEA-2020:1691 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: libva. 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/ALEA-2020-1691/ (Markdown: https://insights.sbomify.com/ALEA-2020-1691/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALEA-2020:1691

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