cve.bz

CVE-2024-36347 (EntrySign)

6.4 mediumEPSS 0.1%

Known as EntrySign

Medium (6.4). EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
Improper signature verification in AMD CPU ROM microcode patch loader may allow an attacker with local administrator privilege to load malicious microcode, potentially resulting in loss of integrity of x86 instruction execution, loss of confidentiality and integrity of data in x86 CPU privileged context and compromise of SMM execution environment.

Severity

CVSS 3.1

6.4 medium
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-07-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-36347 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-36347?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-36347?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-36347 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu14.04:LTS, 26.04:LTS, 26.10amd64-microcodeno fix listedUBUNTU-CVE-2024-36347
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2024-36347
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2024-36347
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 27 moreno fix listedUBUNTU-CVE-2024-36347
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 48 moreno fix listedUBUNTU-CVE-2024-36347
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2024-36347 USN-8179-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1059.65~22.04.1UBUNTU-CVE-2024-36347 USN-8440-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2024-36347
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1054.57~22.04.1UBUNTU-CVE-2024-36347 USN-8179-4
Ubuntu22.04:LTSlinux-hwe-6.8, linux-riscv-6.86.8.0-110.110~22.04.1UBUNTU-CVE-2024-36347 USN-8179-3
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1051.51~22.04.1UBUNTU-CVE-2024-36347 USN-8179-3
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-110.110.1~22.04.1UBUNTU-CVE-2024-36347 USN-8179-1
50 more for Ubuntu in the JSON and on Ubuntu's page.

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat has very limited to no visibility and control over binary blobs provided by third-party vendors. Red Hat relies heavily on the vendors to provide timely updates and information about included changes for this content and in most cases merely acts as a release vehicle between the third-party vendor and Red Hat customers with no possibility of influencing or even documenting the changes. Unless explicitly stated, the level of insight, oversight, and control Red Hat has does not meet the criteria required (in terms of Red Hat ownership of development processes, QA, and documentation) for releasing this content as a RHSA. For more information, please contact the binary content vendor.

AMD believes this issue is caused by a weakness in the signature verification algorithm and the vulnerability could allow an administrator privileged attacker, the ability to load arbitrary CPU microcode patches.

Malicious CPU microcode results in loss of integrity of x86 instruction execution, loss of confidentiality and integrity of data in x86 CPU privileged context and compromise of SMM execution environment.

Red Hat's mitigation

Mitigation requires updating the BIOS for updating the CPU firmware. The bug affects hardware in processors of the AMD EPYC™ family: Naples, Rome, Milan, Milan-X, Genoa, Genoa-X, Bergamo/Siena and Raphael.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-36347.

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON