# ALEA-2020:5501: openscap bug fix and enhancement update

> This update fixes bugs in the OpenSCAP library related to YAML probes and profile building, with no specific security vulnerability described.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 15 Dec 2020

## What is ALEA-2020:5501?

ALEA-2020:5501 is a vulnerability in openscap-engine-sce-devel, published on 15 Dec 2020. 

### Official description

The OpenSCAP suite enables integration of the Security Content Automation
Protocol (SCAP) line of standards. The openscap packages provide the
OpenSCAP library and the oscap utility that provides various SCAP
capabilities.

Bug Fix(es) and Enhancement(s):

* Enable YAML probe to work with sets of values (BZ#1895715)

* Can't build profile with specific platform set (BZ#1896676)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openscap-engine-sce-devel` | AlmaLinux:8 | All versions | 1.3.3-6.el8_3.alma |

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

Apply the vendor's patch.

## Is ALEA-2020:5501 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALEA-2020:5501 is a vulnerability in openscap-engine-sce-devel, published on 15 Dec 2020. 
Exploitation: There is no known exploitation of ALEA-2020:5501 in the wild and no public exploit code.

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

## Sources

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

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