# ALBA-2022:0883: cloud-init bug fix and enhancement update

> This update fixes cloud-init configuration failures on Azure and adds VMware guestinfo support for AlmaLinux 8.

- **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 Mar 2022

## What is ALBA-2022:0883?

ALBA-2022:0883 is a vulnerability in cloud-init, published on 15 Mar 2022. 

### Official description

The cloud-init packages provide a set of init scripts for cloud instances.
Cloud instances need special scripts to run during initialization to
retrieve and install SSH keys, and to let the user run various scripts.

Bug Fix(es) and Enhancement(s):

* [AlmaLinux8] [Azure] cloud-init fails to configure the system (BZ#2040690)

* [cloud-init][AlmaLinux8] Support for cloud-init datasource
'cloud-init-vmware-guestinfo' (BZ#2040704)

## Which versions are affected by ALBA-2022:0883?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cloud-init` | AlmaLinux:8 | All versions | 21.1-7.el8_5.4.alma |

## How do I fix ALBA-2022:0883?

Apply the vendor's patch.

## Is ALBA-2022:0883 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2022:0883 is a vulnerability in cloud-init, published on 15 Mar 2022. 
Exploitation: There is no known exploitation of ALBA-2022:0883 in the wild and no public exploit code.

Affected product: cloud-init. 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-2022-0883/ (Markdown: https://insights.sbomify.com/ALBA-2022-0883/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2022:0883

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