dbcve.org
Milanpi Sp3 FirmwareOperating system · Amd

CVE-2022-23813

MEDIUM · 5.3 CVSS v3.1 Published 2023-01-11
Fix available
A fix is available. Upgrade to 1.0.0.e / 1.0.0.9 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
The software interfaces to ASP and SMU may not enforce the SNP memory security policy resulting in a potential loss of integrity of guest memory in a confidential compute environment.

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

This vulnerability exists in software interfaces to ASP (Application Service Provider) and SMU (System Management Unit) that fail to enforce AMD's SNP (Secure Nested Paging) memory security policy. This allows potential integrity compromise of guest memory in confidential compute environments using AMD SEV-SNP (Secure Encrypted Virtualization with Secure Nested Paging).

MitigationEnsure ASP and SMU interfaces enforce SNP memory security policies; update firmware/BIOS to latest AMD AGESA versions that properly implement SNP policy enforcement; verify hypervisor configuration enables SEV-SNP with appropriate memory integrity controls.

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
Milanpi Sp3 FirmwareOperating system
Affected:< 1.0.0.9
Romepi FirmwareOperating system
Affected:< 1.0.0.e

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

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 AMD processor model
    Run 'dmidecode -t processor | grep -E "Family|Model"' or check /proc/cpuinfo for AMD EPYC processor family. Confirm if it's a 2nd Gen (Rome) or 3rd Gen (Milan) EPYC processor.
    Affected if Processor is AMD EPYC Rome or Milan family.
  2. Check BIOS/firmware version
    Run 'dmidecode -s bios-version' or check the SMU/AGESA firmware version through vendor-specific tools like 'amd_smu_info' or through BMC/IPMI interfaces. Compare against affected versions: Milanpi Sp3 < 1.0.0.9, Romepi < 1.0.0.e.
    Affected if Firmware version is below 1.0.0.9 for Milan or below 1.0.0.e for Rome processors.
  3. Verify SEV-SNP is enabled
    Check hypervisor configuration and system boot parameters. For KVM, run 'grep -i sev /proc/cmdline' or use 'virt-host-validate'. Check for 'sev=1' or 'sev-snp=1' in boot config. On host: 'cat /sys/kernel/mm/amd_sev_snp' or similar SEV-SNP status nodes.
    Affected if SEV-SNP is enabled and running with affected firmware versions.
  4. Check ASP and SMU interface configuration
    Inspect system management interface configuration through BMC (IPMI) or AMD-specific management tools. Verify if ASP and SMU interfaces are exposed and accessible in the system.
    Affected if ASP or SMU management interfaces are present and active on the system.

System is affected if running AMD EPYC Rome or Milan processor with firmware below the specified thresholds AND SEV-SNP is enabled for confidential computing workloads.

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.0.e / 1.0.0.9 or later
Fixed in 1.0.0.e1.0.0.9
Interim mitigation

Ensure ASP and SMU interfaces enforce SNP memory security policies; update firmware/BIOS to latest AMD AGESA versions that properly implement SNP policy enforcement; verify hypervisor configuration enables SEV-SNP with appropriate memory integrity controls.

Recommended fix High confidence

Milanpi Sp3: Firmware >= 1.0.0.9 | Romepi: Firmware >= 1.0.0.e

  1. Identify whether the system is Milanpi Sp3 or Romepi hardware variant
  2. Check current firmware version on the affected system
  3. Obtain the appropriate AMD firmware update: Milanpi Sp3 requires version 1.0.0.9 or later; Romepi requires version 1.0.0.e or later
  4. Download the firmware update package from the official AMD support website (www.amd.com)
  5. Apply the firmware update following AMD's standard firmware update procedures for the specific platform
  6. Reboot the system as required by the update process
  7. Verify the firmware has been updated to the correct version and that the SNP memory security policy is now enforced

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Milanpi Sp3 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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