SUSE-SU-2020:2258-1 Security update for fwupd
Not scored
Published
Check this codebase for SUSE-SU-2020:2258-1 and fix it if it is affected.
What it is: SUSE-SU-2020:2258-1 is a vulnerability in fwupd, published on 18 Aug 2020.
Exploitation: There is no known exploitation of SUSE-SU-2020:2258-1 in the wild and no public exploit code.
Affected product: fwupd. 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-2020-2258-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2020-2258-1/index.md)
An attacker could bypass UEFI Secure Boot restrictions due to an outdated signing key in the fwupd package.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- Available
What is SUSE-SU-2020:2258-1?
SUSE-SU-2020:2258-1 is a vulnerability in fwupd, published on 18 Aug 2020.
Official description
This update of fwupd fixes the following issue:
- rebuild with new UEFI signing key (bsc#1174543)
Which versions are affected by SUSE-SU-2020:2258-1?
Linux distribution packages (1)
fwupd SUSE:Linux Enterprise Module for Desktop Applications 15 SP2 | All versions | 1.2.11-5.2.1 |
How do I fix SUSE-SU-2020:2258-1?
Apply the vendor's patch.
Is SUSE-SU-2020:2258-1 being exploited?
There is no known exploitation of SUSE-SU-2020:2258-1 in the wild and no public exploit code.