# ALBA-2022:4697: cloud-init bug fix update

> Cloud-init failed to handle SSH keys with carriage returns, preventing instance initialization on Azure; this update fixes the parsing logic.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 May 2022

## What is ALBA-2022:4697?

ALBA-2022:4697 is a vulnerability in cloud-init, published on 23 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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:

* Previously, cloud-init incorrectly handled SSH keys containing \r\n characters. As a consequence, cloud-init could not be used in Microsoft Azure. This update has changed how cloud-init handles SSH keys so the described keys work as expected in Azure. (BZ#2088028)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cloud-init` | AlmaLinux:8 | All versions | 21.1-15.el8.alma |

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

Apply the vendor's patch.

## Is ALBA-2022:4697 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2022:4697 is a vulnerability in cloud-init, published on 23 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of ALBA-2022:4697 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-4697/ (Markdown: https://insights.sbomify.com/ALBA-2022-4697/index.md)
```

## Sources

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

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