dbcve.org
Athlon Silver 3050u FirmwareOperating system · Amd

CVE-2022-23815

HIGH · 8.2 CVSS v3.1 Published 2024-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
Improper bounds checking in APCB firmware may allow an attacker to perform an out of bounds write, corrupting the APCB entry, potentially leading to arbitrary code execution.

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

Improper bounds checking in APCB firmware allows an attacker to perform out-of-bounds write operations, corrupting APCB entries. This can potentially lead to arbitrary code execution in the firmware context.

MitigationApply vendor-provided firmware updates addressing the bounds checking vulnerability in APCB. Until patches are available, restrict physical access to affected systems and monitor for firmware tampering.

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
Athlon Silver 3050u FirmwareOperating system
Affected:< picassopi-fp5_1.0.0.e
Athlon Gold 3150u FirmwareOperating system
Affected:< picassopi-fp5_1.0.0.e
Ryzen 7 3780u FirmwareOperating system
Affected:< picassopi-fp5_1.0.0.e
Ryzen 7 3750h FirmwareOperating system
Affected:< picassopi-fp5_1.0.0.e
Ryzen 7 Pro 3700u FirmwareOperating system
Affected:< picassopi-fp5_1.0.0.e
Ryzen 7 3700u FirmwareOperating system
Affected:< picassopi-fp5_1.0.0.e
Ryzen 5 3580u FirmwareOperating system
Affected:< picassopi-fp5_1.0.0.e
Ryzen 5 3550h FirmwareOperating system
Affected:< picassopi-fp5_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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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 the CPU model
    Run 'wmic cpu get name' on Windows or 'cat /proc/cpuinfo' on Linux to identify the AMD processor
    Affected if The CPU is an Amd Athlon Silver 3050u, Athlon Gold 3150u, Ryzen 7 3780u, Ryzen 7 3750h, Ryzen 7 Pro 3700u, Ryzen 7 3700u, Ryzen 5 3580u, or Ryzen 5 3550h
  2. Check the firmware version
    Access UEFI/BIOS setup during boot and note the BIOS/UEFI version, or run 'dmidecode -s bios-version' on Linux or 'wmic bios get smbiosbiosversion' on Windows
    Affected if The firmware version is less than picassopi-fp5_1.0.0.e (any version before this release)
  3. Inspect APCB firmware structure
    Use UEFI firmware analysis tools (such as UEFITool or chipsec) to extract and examine the APCB data structure within the firmware image
    Affected if The APCB region shows signs of corruption, unexpected entries, or data inconsistency indicating out-of-bounds write manipulation

A system is affected if it contains one of the listed AMD processors AND is running firmware versions earlier than picassopi-fp5_1.0.0.e, allowing the improper bounds checking vulnerability in APCB to be exploited.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided firmware updates addressing the bounds checking vulnerability in APCB. Until patches are available, restrict physical access to affected systems and monitor for firmware tampering.

Recommended fix High confidence

picassopi-fp5_1.0.0.e or later

  1. Identify the exact AMD processor model and current firmware version installed on the system
  2. Visit www.amd.com and navigate to the support/drivers section for the specific processor or device
  3. Download the latest BIOS/firmware update labeled picassopi-fp5_1.0.0.e or later
  4. Apply the firmware update following AMD's documented update process (typically via BIOS update utility or flashing tool)
  5. Reboot the system and verify the installed firmware version is picassopi-fp5_1.0.0.e or higher
Caveat Firmware updates carry risk of system incompatibility; ensure backup and follow vendor update procedures precisely

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

Fix this in Athlon Silver 3050u Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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