{"answers":{"affected":"It affects 13 products.","exploited":"There is no known exploitation of CVE-2025-62862 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-62862 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-62862 is a medium-severity memory corruption vulnerability in n/a, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-62862 and fix it if it is affected.\n\nWhat it is: CVE-2025-62862 is a medium-severity memory corruption vulnerability in n/a, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-62862 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-62862/ (Markdown: https://insights.sbomify.com/CVE-2025-62862/index.md)","id":"CVE-2025-62862","markdown":"https://insights.sbomify.com/CVE-2025-62862/index.md","name":"CVE-2025-62862","record":{"aliases":["GHSA-rw9h-q55r-xq4f"],"analysis":{"component_type":"hardware_firmware","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AmpereOne firmware","requires_auth":"high_privilege","summary":"An incorrectly formed SMC call in AmpereOne UEFI-MM drivers allows out-of-bounds reads leaking secure information or writes corrupting memory.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ampereone_a128-34x_firmware","vendor":"amperecomputing"},{"product":"ampereone_a144-24x_firmware","vendor":"amperecomputing"},{"product":"ampereone_a144-26m_firmware","vendor":"amperecomputing"},{"product":"ampereone_a144-27x_firmware","vendor":"amperecomputing"},{"product":"ampereone_a144-33m_firmware","vendor":"amperecomputing"},{"product":"ampereone_a160-28m_firmware","vendor":"amperecomputing"},{"product":"ampereone_a160-28x_firmware","vendor":"amperecomputing"},{"product":"ampereone_a192-26m_firmware","vendor":"amperecomputing"},{"product":"ampereone_a192-26x_firmware","vendor":"amperecomputing"},{"product":"ampereone_a192-32m_firmware","vendor":"amperecomputing"},{"product":"ampereone_a192-32x_firmware","vendor":"amperecomputing"},{"product":"ampereone_a96-36m_firmware","vendor":"amperecomputing"},{"product":"ampereone_a96-36x_firmware","vendor":"amperecomputing"}],"cvss":{"score":4.6,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2025-62862","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2025-62863"},"packages":[],"prev":{"headline":"QTS, QuTS hero","id":"CVE-2025-62858"},"products":["n/a"],"published":"2025-12-16","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-62863","kev_date_added":null,"published":"2025-12-16"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-62864","kev_date_added":null,"published":"2025-12-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-17","vendors":["n/a"]},"summary":"An incorrectly formed SMC call in AmpereOne UEFI-MM drivers allows out-of-bounds reads leaking secure information or writes corrupting memory.","url":"https://insights.sbomify.com/CVE-2025-62862/"}