{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2019-6260 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-6260 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-6260 is a critical vulnerability in n/a, published on 22 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-6260 and fix it if it is affected.\n\nWhat it is: CVE-2019-6260 is a critical vulnerability in n/a, published on 22 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-6260 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-2019-6260/ (Markdown: https://insights.sbomify.com/CVE-2019-6260/index.md)","id":"CVE-2019-6260","markdown":"https://insights.sbomify.com/CVE-2019-6260/index.md","name":"CVE-2019-6260","record":{"aliases":["GHSA-3qf3-2r2j-47g4"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"ASPEED BMC firmware","requires_auth":"none","summary":"ASPEED BMC firmware allows arbitrary memory access from the host via AHB bridges, enabling code execution and data manipulation.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ast2400_firmware","vendor":"aspeedtech"},{"product":"ast2500_firmware","vendor":"aspeedtech"},{"product":"fas\\/aff_baseboard_management_controller","vendor":"netapp"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"The ASPEED ast2400 and ast2500 Baseband Management Controller (BMC) hardware and firmware implement Advanced High-performance Bus (AHB) bridges, which allow arbitrary read and write access to the BMC's physical address space from the host (or from the network in unusual cases where the BMC console uart is attached to a serial concentrator). This CVE applies to the specific cases of iLPC2AHB bridge Pt I, iLPC2AHB bridge Pt II, PCIe VGA P2A bridge, DMA from/to arbitrary BMC memory via X-DMA, UART-based SoC Debug interface, LPC2AHB bridge, PCIe BMC P2A bridge, and Watchdog setup.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2021-05-21","github_poc":1,"max_poc_stars":6,"metasploit":0,"nuclei":0,"refs":[{"date":"2021-05-21T09:01:05Z","kind":"github_poc","ref":"https://github.com/nikitapbst/cve-2019-6260","stars":6,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"Other in n/a","id":"CVE-2019-6260","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-6261"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2019-6259"},"products":["n/a"],"published":"2019-01-22","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"ASPEED BMC firmware allows arbitrary memory access from the host via AHB bridges, enabling code execution and data manipulation.","url":"https://insights.sbomify.com/CVE-2019-6260/"}