{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-1710 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-1710 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1710 is a high-severity vulnerability in Endress+Hauser MEAC300-FNADE4, published on 3 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-1710 and fix it if it is affected.\n\nWhat it is: CVE-2025-1710 is a high-severity vulnerability in Endress+Hauser MEAC300-FNADE4, published on 3 Jul 2025. 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-2025-1710 in the wild and no public exploit code.\n\nAffected product: Endress+Hauser MEAC300-FNADE4. 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-1710/ (Markdown: https://insights.sbomify.com/CVE-2025-1710/index.md)","id":"CVE-2025-1710","markdown":"https://insights.sbomify.com/CVE-2025-1710/index.md","name":"CVE-2025-1710","record":{"aliases":["GHSA-47c4-h5xr-wvg6"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Storage Manager","requires_auth":"none","summary":"Attackers can bypass authentication controls via brute-force attacks due to missing rate limiting, potentially gaining unauthorized access to the storage manager.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SICK AG","cpe":[{"product":"meac300-fnade4_firmware","vendor":"endress"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"The maxView Storage Manager does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it susceptible to brute-force attacks.","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":"CVE-2025-1710","id":"CVE-2025-1710","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"CVE-2025-1711","id":"CVE-2025-1711"},"packages":[],"prev":{"headline":"CVE-2025-1709","id":"CVE-2025-1709"},"products":["Endress+Hauser MEAC300-FNADE4"],"published":"2025-07-03","related":[{"cvss_score":8.6,"headline":"CVE-2025-1708","id":"CVE-2025-1708","kev_date_added":null,"published":"2025-07-03"},{"cvss_score":7.6,"headline":"CVE-2025-27460","id":"CVE-2025-27460","kev_date_added":null,"published":"2025-07-03"},{"cvss_score":7.6,"headline":"CVE-2025-27461","id":"CVE-2025-27461","kev_date_added":null,"published":"2025-07-03"},{"cvss_score":7.5,"headline":"CVE-2025-27449","id":"CVE-2025-27449","kev_date_added":null,"published":"2025-07-03"},{"cvss_score":7.5,"headline":"CVE-2025-27456","id":"CVE-2025-27456","kev_date_added":null,"published":"2025-07-03"},{"cvss_score":7.4,"headline":"CVE-2025-27447","id":"CVE-2025-27447","kev_date_added":null,"published":"2025-07-03"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-03","vendors":["Endress+Hauser"]},"summary":"Attackers can bypass authentication controls via brute-force attacks due to missing rate limiting, potentially gaining unauthorized access to the storage manager.","url":"https://insights.sbomify.com/CVE-2025-1710/"}