dbcve.org
Aptio VOperating system · Ami

CVE-2023-39535

HIGH · 7.8 CVSS v3.1 Published 2023-11-14
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 input validation 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 input validation vulnerability that can be exploited via the local network. This allows a local attacker to potentially compromise the BIOS firmware, leading to loss of confidentiality, integrity and availability of the affected system.

MitigationApply BIOS/firmware updates provided by AMI for AptioV. Implement network segmentation to limit local network access to critical systems and ensure physical security controls are in place.

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. Identify BIOS vendor and version
    On the target system, access the BIOS/UEFI setup utility during boot (typically via DEL, F2, or F12 key) and navigate to the Main or Information section. Record the BIOS vendor (should show 'American Megatrends' or 'AMI') and the BIOS version/date string.
    Affected if The BIOS vendor is American Megatrends and the product name includes 'Aptio V' or 'AptioV' - all such versions are affected by this vulnerability.
  2. Check for network management interfaces
    Determine if the system has a Baseboard Management Controller (BMC), IPMI, or other out-of-band management interface enabled. Run 'ipmitool mc info' or check BIOS settings for 'IPMI', 'BMC', 'Remote Management', or 'Intel AMT' options.
    Affected if A BMC/IPMI or similar network-accessible management interface is present and configured on the network, as the vulnerability is exploitable via the local network.
  3. Verify network accessibility of management interface
    From a system on the same local network, test connectivity to the BMC/IPMI interface using 'ping <BMC-IP>' and verify port accessibility (common ports: 623 UDP for IPMI, 443 for web interfaces). Document the IP address and accessible ports.
    Affected if The BMC or management interface responds to network requests from untrusted local network segments, indicating exposure to local attackers.
  4. Assess physical and network access controls
    Review the network segmentation and physical security controls for the system. Identify whether the management network is shared with untrusted systems or accessible to unauthorized personnel.
    Affected if The system with AptioV BIOS is on a shared or untrusted network segment without proper isolation, or physical access is uncontrolled.

A system is affected if it runs AMI AptioV BIOS with a network-accessible management interface (BMC/IPMI) exposed to an untrusted local network segment.

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 BIOS/firmware updates provided by AMI for AptioV. Implement network segmentation to limit local network access to critical systems and ensure physical security controls are in place.

Fix this in Aptio V Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39535 — 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-39535 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