dbcve.org
Aptio VOperating system · Ami

CVE-2023-34470

HIGH · 7.8 CVSS v3.1 Published 2023-09-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
AMI AptioV contains a vulnerability in BIOS where an Attacker may use an improper access control via the local network. A successful exploit of this vulnerability may lead to a loss of confidentiality, integrity and availability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

AMI AptioV BIOS contains an improper access control vulnerability that can be exploited via the local network. This allows an attacker with local network access to potentially bypass authentication or authorization controls in the BIOS, leading to full compromise of confidentiality, integrity, and availability.

MitigationApply the vendor-provided BIOS firmware update from AMI or the system OEM (Original Equipment Manufacturer) to remediate this vulnerability. Organizations should also restrict network access to management interfaces and ensure proper network segmentation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Aptio VOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm AptioV BIOS is in use
    Access the system BIOS setup utility (typically via F2, Del, or F12 during boot) or use system information tools (like dmidecode on Linux or systeminfo on Windows) to identify the BIOS vendor and version. Look for 'AMI' or 'Aptio' in the BIOS identification strings.
    Affected if The system uses AMI AptioV BIOS (all versions of AptioV are affected)
  2. Identify exposed BIOS management interfaces
    Check if network-accessible BIOS management features are enabled. These may include: IPMI/BMC (check for open port 623 UDP), Serial Over LAN (SOL), KVM over IP, or BIOS configuration network services. Use commands like 'netstat -an | grep -E "(623|5900)"' or port scanners to identify exposed management ports on the system or BMC.
    Affected if Network-accessible BIOS management interfaces (IPMI, SOL, KVM, etc.) are enabled and reachable on the local network
  3. Verify network access controls on management interfaces
    Review network configuration to determine if BIOS management interfaces are on the same network segment as regular workstations or if they are accessible from untrusted network segments. Check VLAN configurations, ACLs, and firewall rules governing access to BMC/IPMI ports.
    Affected if BIOS management interfaces can be accessed from network segments without proper authentication controls or network isolation
  4. Review BIOS configuration for authentication settings
    If accessible, enter the BIOS setup and examine security-related settings. Look for: IPMI authentication settings, BIOS password requirements, Secure Boot status, and TPM configuration. Document whether authentication is enforced for out-of-band management features.
    Affected if BIOS management features do not require strong authentication or allow anonymous/blank credential access

A user is affected if their system runs AMI AptioV BIOS and has network-accessible BIOS management interfaces (like IPMI/SOL) enabled without proper network isolation or access controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided BIOS firmware update from AMI or the system OEM (Original Equipment Manufacturer) to remediate this vulnerability. Organizations should also restrict network access to management interfaces and ensure proper network segmentation.

Fix this in Aptio V Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-34470 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data