CVE-2023-31315 Code injection in 1st Gen AMD EPYC™ Processors
High 7.5
Published
Updated
Check this codebase for CVE-2023-31315 and fix it if it is affected.
What it is: CVE-2023-31315 is a high-severity code injection vulnerability in 1st Gen AMD EPYC™ Processors, published on 9 Aug 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 CVE-2023-31315 in the wild and no public exploit code.
Affected product: 1st Gen AMD EPYC™ Processors. 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/CVE-2023-31315/ (Markdown: https://insights.sbomify.com/CVE-2023-31315/index.md)
A malicious program with ring0 access can modify SMM configuration via improper MSR validation, leading to arbitrary code execution on AMD processors.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-31315?
CVE-2023-31315 is a high-severity code injection vulnerability in 1st Gen AMD EPYC™ Processors, published on 9 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Improper validation in a model specific register (MSR) could allow a malicious program with ring0 access to modify SMM configuration while SMI lock is enabled, potentially leading to arbitrary code execution.
Weakness: CWE-94
Which versions are affected by CVE-2023-31315?
Linux distribution packages (40)
iwl100-firmware Red Hat:enterprise_linux:9::baseos | All versions | 0:39.31.5.1-143.2.el9_4 |
iwl1000-firmware Red Hat:enterprise_linux:9::baseos | All versions | 1:39.31.5.1-143.2.el9_4 |
iwl105-firmware Red Hat:enterprise_linux:9::baseos | All versions | 0:18.168.6.1-143.2.el9_4 |
iwl135-firmware Red Hat:enterprise_linux:9::baseos | All versions | 0:18.168.6.1-143.2.el9_4 |
iwl2000-firmware Red Hat:enterprise_linux:9::baseos | All versions | 0:18.168.6.1-143.2.el9_4 |
iwl2030-firmware Red Hat:enterprise_linux:9::baseos | All versions | 0:18.168.6.1-143.2.el9_4 |
iwl3160-firmware Red Hat:enterprise_linux:9::baseos | All versions | 1:25.30.13.0-143.2.el9_4 |
iwl5000-firmware Red Hat:enterprise_linux:9::baseos | All versions | 0:8.83.5.1_1-143.2.el9_4 |
iwl5150-firmware Red Hat:enterprise_linux:9::baseos | All versions | 0:8.24.2.2-143.2.el9_4 |
iwl6000g2a-firmware Red Hat:enterprise_linux:9::baseos | All versions | 0:18.168.6.1-143.2.el9_4 |
iwl6000g2b-firmware Red Hat:enterprise_linux:9::baseos | All versions | 0:18.168.6.1-143.2.el9_4 |
iwl6050-firmware Red Hat:enterprise_linux:9::baseos | All versions | 0:41.28.5.1-143.2.el9_4 |
iwl7260-firmware Red Hat:enterprise_linux:9::baseos | All versions | 1:25.30.13.0-143.2.el9_4 |
libertas-sd8787-firmware Red Hat:enterprise_linux:9::baseos | All versions | 0:20240716-143.2.el9_4 |
linux-firmware Red Hat:enterprise_linux:9::baseos | All versions | 0:20240716-143.2.el9_4 |
linux-firmware-whence Red Hat:enterprise_linux:9::baseos | All versions | 0:20240716-143.2.el9_4 |
netronome-firmware Red Hat:enterprise_linux:9::baseos | All versions | 0:20240716-143.2.el9_4 |
iwl100-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:39.31.5.1-76.el7_7 |
iwl1000-firmware Red Hat:rhel_aus:7.7::server | All versions | 1:39.31.5.1-76.el7_7 |
iwl105-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:18.168.6.1-76.el7_7 |
iwl135-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:18.168.6.1-76.el7_7 |
iwl2000-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:18.168.6.1-76.el7_7 |
iwl2030-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:18.168.6.1-76.el7_7 |
iwl3160-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:22.0.7.0-76.el7_7 |
iwl3945-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:15.32.2.9-76.el7_7 |
iwl4965-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:228.61.2.24-76.el7_7 |
iwl5000-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:8.83.5.1_1-76.el7_7 |
iwl5150-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:8.24.2.2-76.el7_7 |
iwl6000-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:9.221.4.1-76.el7_7 |
iwl6000g2a-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:17.168.5.3-76.el7_7 |
iwl6000g2b-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:17.168.5.2-76.el7_7 |
iwl6050-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:41.28.5.1-76.el7_7 |
iwl7260-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:22.0.7.0-76.el7_7 |
iwl7265-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:22.0.7.0-76.el7_7 |
linux-firmware Red Hat:rhel_aus:7.7::server | All versions | 0:20190429-76.gitddde598.el7_7 |
iwl100-firmware Red Hat:rhel_e4s:9.0::baseos | All versions | 0:39.31.5.1-131.el9_0 |
iwl1000-firmware Red Hat:rhel_e4s:9.0::baseos | All versions | 1:39.31.5.1-131.el9_0 |
iwl105-firmware Red Hat:rhel_e4s:9.0::baseos | All versions | 0:18.168.6.1-131.el9_0 |
iwl135-firmware Red Hat:rhel_e4s:9.0::baseos | All versions | 0:18.168.6.1-131.el9_0 |
iwl2000-firmware Red Hat:rhel_e4s:9.0::baseos | All versions | 0:18.168.6.1-131.el9_0 |
How do I fix CVE-2023-31315?
Apply the vendor's patch.
Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.
Is CVE-2023-31315 being exploited?
There is no known exploitation of CVE-2023-31315 in the wild and no public exploit code.
Sources
Also known as CLSA-2024-1728477985, CLSA-2024-1728478701, CLSA-2024-1728579854, CLSA-2024-1728581276, CLSA-2024-1728581726, CLSA-2024-1728582568 and 22 more.