{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-0036 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-0036 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-0036 is a low-severity vulnerability in AMD Alveo V80 Compute Accelerator, published on 9 Jun 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-0036 and fix it if it is affected.\n\nWhat it is: CVE-2025-0036 is a low-severity vulnerability in AMD Alveo V80 Compute Accelerator, published on 9 Jun 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-0036 in the wild and no public exploit code.\n\nAffected product: AMD Alveo V80 Compute Accelerator. 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-0036/ (Markdown: https://insights.sbomify.com/CVE-2025-0036/index.md)","id":"CVE-2025-0036","markdown":"https://insights.sbomify.com/CVE-2025-0036/index.md","name":"CVE-2025-0036","record":{"aliases":["GHSA-55hh-327m-68hj"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AMD Versal SoC","requires_auth":"low_privilege","summary":"Incorrect SSS configuration in AMD Versal SoCs causes cryptographic data to be written to or read from invalid locations, leading to data integrity and confidentiality issues.","user_interaction":"required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMD","cpe":[],"cvss":{"score":3.2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-941","name":"Incorrectly Specified Destination in a Communication Channel"},{"id":"CWE-940","name":"Improper Verification of Source of a Communication Channel"},{"id":"CWE-772","name":"Missing Release of Resource after Effective Lifetime"},{"id":"CWE-682","name":"Incorrect Calculation"},{"id":"CWE-497","name":"Exposure of Sensitive System Information to an Unauthorized Control Sphere"}],"description":"In AMD Versal Adaptive SoC devices, the incorrect configuration of the SSS during runtime (post-boot) cryptographic operations could cause data to be incorrectly written to and read from invalid locations as well as returning incorrect cryptographic data.","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":"Misconfiguration in Alveo V80 Compute Accelerator","id":"CVE-2025-0036","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Platform Loader and Manager (PLM)","id":"CVE-2025-0037"},"packages":[],"prev":{"headline":"Privilege escalation in AMD Cloud Manageability Service","id":"CVE-2025-0035"},"products":["Alveo V80 Compute Accelerator","Versal AI Core Series","Versal AI Edge Series","Versal Adaptive SoC Devices","Versal HBM Series","Versal Premium Series","Versal Prime Series","Versal RF Series"],"published":"2025-06-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-06-30","vendors":["AMD"]},"summary":"Incorrect SSS configuration in AMD Versal SoCs causes cryptographic data to be written to or read from invalid locations, leading to data integrity and confidentiality issues.","url":"https://insights.sbomify.com/CVE-2025-0036/"}