{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-2860 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-2860 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-2860 is a medium-severity vulnerability in Arteche saTECH BCU, published on 28 Mar 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-2860 and fix it if it is affected.\n\nWhat it is: CVE-2025-2860 is a medium-severity vulnerability in Arteche saTECH BCU, published on 28 Mar 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-2860 in the wild and no public exploit code.\n\nAffected product: Arteche saTECH BCU. 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-2860/ (Markdown: https://insights.sbomify.com/CVE-2025-2860/index.md)","id":"CVE-2025-2860","markdown":"https://insights.sbomify.com/CVE-2025-2860/index.md","name":"CVE-2025-2860","record":{"aliases":["GHSA-x542-2cq7-f2p3"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"saTECH BCU firmware","requires_auth":"low_privilege","summary":"An authenticated attacker can access sensitive user credentials from an XML file in saTECH BCU firmware by knowing the file path.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCIBE","cpe":[{"product":"satech_bcu_firmware","vendor":"arteche"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"SaTECH BCU in its firmware version 2.1.3, allows an authenticated attacker to access information about the credentials that users have within the web (.xml file). In order to exploit this vulnerability, the attacker must know the path, regardless of the user's privileges on the website.","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":"Exposure of Sensitive Information vulnerability in saTECH BCU","id":"CVE-2025-2860","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cleartext Transmission of Sensitive Information vulnerability in saTECH BCU","id":"CVE-2025-2861"},"packages":[],"prev":{"headline":"Improper Authentication vulnerability in saTECH BCU","id":"CVE-2025-2859"},"products":["saTECH BCU"],"published":"2025-03-28","related":[{"cvss_score":8.5,"headline":"Privilege escalation vulnerability in saTECH BCU","id":"CVE-2025-2858","kev_date_added":null,"published":"2025-03-28"},{"cvss_score":6.9,"headline":"Improper Authentication vulnerability in saTECH BCU","id":"CVE-2025-2859","kev_date_added":null,"published":"2025-03-28"},{"cvss_score":6.9,"headline":"Cleartext Transmission of Sensitive Information vulnerability in saTECH BCU","id":"CVE-2025-2861","kev_date_added":null,"published":"2025-03-28"},{"cvss_score":6.9,"headline":"Weak Encoding for Password vulnerability in saTECH BCU","id":"CVE-2025-2862","kev_date_added":null,"published":"2025-03-28"},{"cvss_score":5.7,"headline":"Cross-site request forgery (CSRF) vulnerability in saTECH BCU","id":"CVE-2025-2863","kev_date_added":null,"published":"2025-03-28"},{"cvss_score":2.4,"headline":"Reflected Cross-Site Scripting (XSS) vulnerability in saTECH BCU","id":"CVE-2025-2865","kev_date_added":null,"published":"2025-03-28"}],"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-03-28","vendors":["Arteche"]},"summary":"An authenticated attacker can access sensitive user credentials from an XML file in saTECH BCU firmware by knowing the file path.","url":"https://insights.sbomify.com/CVE-2025-2860/"}