# SUSE-SU-2024:1867-1: Security update for fwupdate

> An update to fwupdate addresses secure boot key issues and memory permission warnings, ensuring proper secure boot enforcement on SUSE systems.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 May 2024

## What is SUSE-SU-2024:1867-1?

SUSE-SU-2024:1867-1 is a vulnerability in fwupdate, published on 30 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This update of fwupdate fixes the following issues:

- rebuild the package with the new secure boot key (bsc#1209188).
- Update the email address of security team in SBAT (bsc#1221301)
- elf_aarch64_efi.lds: set the memory permission explicitly to
  avoid ld warning like 'LOAD segment with RWX permissions'

## Which versions are affected by SUSE-SU-2024:1867-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fwupdate` | SUSE:Enterprise Storage 7 | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Enterprise Storage 7.1 | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Linux Enterprise Micro 5.5 | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Manager Proxy 4.3 | All versions | 12-150100.11.15.2 |
| `fwupdate` | SUSE:Manager Server 4.3 | All versions | 12-150100.11.15.2 |
| `fwupdate` | openSUSE:Leap 15.5 | All versions | 12-150100.11.15.2 |
| `fwupdate` | openSUSE:Leap 15.6 | All versions | 12-150100.11.15.2 |

## How do I fix SUSE-SU-2024:1867-1?

Apply the vendor's patch.

## Is SUSE-SU-2024:1867-1 being exploited?

There is no known exploitation of SUSE-SU-2024:1867-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2024:1867-1 and fix it if it is affected.

What it is: SUSE-SU-2024:1867-1 is a vulnerability in fwupdate, published on 30 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2024:1867-1 in the wild and no public exploit code.

Affected product: fwupdate. 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/SUSE-SU-2024-1867-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2024-1867-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2024:1867-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2024-1867-1/
Summaries are generated and may contain mistakes; the official description above is the record.