CVE-2024-2315 is a high severity (7.1) improper access control flaw in AMI Aptio V BIOS. A local attacker may modify SPI flash and launch a BIOS boot kit. Check AMI advisory AMI-SA-2024004 and your device maker for a firmware update. NVD published it on 2024-11-12.
Weakness: CWE-284 (Improper Access Control).
What's affected
- Affected: AMI Aptio V (APTIOV) BIOS. The record gives no version list.
- Fixed: not named in the record. The AMI security advisory AMI-SA-2024004 is the place to look, and your OEM decides which firmware build carries the fix.
- Attack conditions:
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H, meaning the attacker is local and needs a low-privilege account, with no user interaction.
The record says successful exploitation may lead to unexpected SPI flash modifications and BIOS boot kit launches, and may affect availability. We did not retrieve the AMI PDF, so confirm details there.
How to check if you're exposed
Firmware is not reported by a package manager, so use the system tools.
- Read your BIOS vendor and version: on Linux run
sudo dmidecode -t bios, and on Windows runGet-CimInstance Win32_BIOSin PowerShell. - Compare against your hardware vendor's advisory page for AMI-SA-2024004 and CVE-2024-2315.
- Check whether firmware write protection and Secure Boot are enabled in your settings.
What to do now
- Identify which device models in your fleet use AMI Aptio V and record their BIOS versions.
- Open the OEM advisory for each model and install the BIOS update that cites this CVE, following the maker's instructions.
- Limit who has local administrator or physical access to machines until firmware is updated.
- Enable Secure Boot and firmware write protection where the hardware supports it.
- Add firmware versions to your asset inventory so the next advisory is easier to match.
Why it matters
The record classes this as CWE-284 (Improper Access Control). Firmware sits below the operating system, so a flaw that allows writes to the flash chip can let an attacker persist through reinstalls and hide from OS level tools. That is why a local-only issue still earns attention.
The score is 7.1 (High). The KEV flag is false. The record, published on 2024-11-12, does not claim exploitation in the wild.
Quick check
Is there a single fixed BIOS version?
No. The record does not name one. Firmware builds come from each hardware maker, so use the AMI advisory and your OEM's page.
Does it need physical access?
The vector says local access with a low-privilege account. The record does not say that physical access is required.
Sources
- CVE-2024-2315 record on Safeguard Gold
- NVD description and CVSS vector for CVE-2024-2315, as held in the batch record
- AMI security advisory AMI-SA-2024004 (PDF, linked from the record; not retrieved for this post)
Last reviewed: 19 October 2026.
