Categories
CVE-2025-62862 medium CVSS 4.6

Out-of-Bounds Read in Ampere AmpereOne AC03 devices (CVE-2025-62862)

Summary

Vulnerability in Ampere AmpereOne AC03 devices (CVE-2025-62862). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

Ampere AmpereOne AC03 devices before 3.5.9.3, AmpereOne AC04 devices before 4.4.5.2, and AmpereOne M devices before 5.4.5.1 allow an incorrectly formed SMC call to UEFI-MM Boot Error Record Table driver that could result in (1) an out-of-bounds read which leaks Secure-EL0 information to a process running in Non-Secure state or (2) an out-of-bounds write which corrupts Secure or Non-Secure memory, limited to memory mapped to UEFI-MM Secure Partition by the Secure Partition Manager.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-62862 has been found in Ampere AmpereOne AC03 devices.
Risk of unauthorized operations or information disclosure. CVSS score: 4.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Ampere AmpereOne AC03 devices CVE-2025-62862" on the vendor's site.

CVE-2025-62862 (Ampere AmpereOne AC03 devices) — CWE-125 / CVSS v3 4.6
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Out-of-bounds read (CWE-125) exists in Ampere AmpereOne AC03 devices.

📍 Affected scope

Check the vendor advisory for the affected versions of Ampere AmpereOne AC03 devices.

🔥 Severity

Severity: Medium (CVSS 4.6/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Ampere AmpereOne AC03 devices を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details