Sensitive Information Exposure in Intel Microcode: CVE-2024-45332

intel-ucode Updated 02 Oct 2025

Summary

13/05/2025
N/A
Yes i
Unrated
Not published

CVE-2024-45332: Exposure of sensitive information caused by shared microarchitectural predictor state that influences transient execution in the indirect branch predictors for some Intel(R) Processors may allow an authenticated user to... Affects intel-ucode versions < 20250512-r0. Fixed in 20250512-r0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

Intel Microcode is a critical component of Intel processors that provides low-level control and updates to the processor's functionality. It is responsible for implementing various features and optimizations, ensuring the processor operates efficiently and securely. However, certain vulnerabilities can expose sensitive information, particularly through shared microarchitectural states, which can be exploited if not addressed promptly.

Vulnerability Detail

CVE-2024-45332 is a vulnerability that arises from the exposure of sensitive information due to shared microarchitectural predictor state. This state can influence transient execution in the indirect branch predictors of some Intel processors. An authenticated user with local access may exploit this vulnerability to potentially enable information disclosure, leading to unauthorized access to sensitive data. The vulnerability affects multiple versions of the Intel microcode across Debian ecosystems, making it critical for users to be aware and take action.

How To Fix

Minimum fixed version

20250512-r0

This is the first release that contains the fix.

sudo apk add --upgrade intel-ucode

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, users can limit local access to the affected systems and ensure that only trusted users have authenticated access. Additionally, monitoring system logs for unusual activity may help in identifying potential exploitation attempts.

Conclusion

CVE-2024-45332 represents a significant risk for users of Intel Microcode, particularly in Debian environments. It is crucial to update to the latest patched version to mitigate the risk of sensitive information exposure. Users should also consider implementing workarounds to enhance security while awaiting updates.

See every vulnerability recorded for intel-ucode →

Share this vulnerability

FAQ

CVE-2024-45332 is a vulnerability in Intel Microcode that allows for potential information disclosure due to shared microarchitectural predictor state.

Users of Intel processors running the affected versions of Intel Microcode on Debian 11, 12, and 13 are at risk.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If updating is not possible, consider implementing strict access controls and monitoring for unusual activity as a temporary measure.

More details can be found in the official CVE database and through security advisories related to Intel Microcode.

Related vulnerabilities

Recent vulnerabilities recorded for intel-ucode.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Minimum fixed version

20250512-r0

This is the first release that contains the fix.

sudo apk add --upgrade intel-ucode

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback