{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-35434 exists.","fix":"No fix has been published for CVE-2025-35434 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-35434 is a low-severity vulnerability in CISA Thorium, published on 17 Sep 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-35434 and fix it if it is affected.\n\nWhat it is: CVE-2025-35434 is a low-severity vulnerability in CISA Thorium, published on 17 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-35434 exists.\n\nAffected product: CISA Thorium. 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-35434/ (Markdown: https://insights.sbomify.com/CVE-2025-35434/index.md)","id":"CVE-2025-35434","markdown":"https://insights.sbomify.com/CVE-2025-35434/index.md","name":"CVE-2025-35434","record":{"aliases":["GHSA-r8gr-36v8-m732"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CISA Thorium","requires_auth":"none","summary":"An attacker can impersonate the Elasticsearch service by bypassing TLS validation, potentially intercepting or modifying data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisa-cg","cpe":[{"product":"thorium","vendor":"cisa"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"CISA Thorium does not validate TLS certificates when connecting to Elasticsearch. An unauthenticated attacker with access to a Thorium cluster could impersonate the Elasticsearch service. Fixed in 1.1.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"CISA Thorium does not validate TLS connections to Elasticsearch","id":"CVE-2025-35434","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"CISA Thorium download stream divide by zero","id":"CVE-2025-35435"},"packages":[],"prev":{"headline":"CISA Thorium does not properly invalidate previously used tokens","id":"CVE-2025-35433"},"products":["Thorium"],"published":"2025-09-17","related":[{"cvss_score":6.9,"headline":"CISA Thorium does not rate limit account verification email messages","id":"CVE-2025-35432","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":6.9,"headline":"CISA Thorium account verification email error handling","id":"CVE-2025-35436","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":5.3,"headline":"CISA Thorium insecure downloaded file path validation","id":"CVE-2025-35430","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":5.3,"headline":"CISA Thorium LDAP injection","id":"CVE-2025-35431","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":5.3,"headline":"CISA Thorium download stream divide by zero","id":"CVE-2025-35435","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":2.3,"headline":"CISA Thorium does not properly invalidate previously used tokens","id":"CVE-2025-35433","kev_date_added":null,"published":"2025-09-17"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-30","vendors":["CISA"]},"summary":"An attacker can impersonate the Elasticsearch service by bypassing TLS validation, potentially intercepting or modifying data.","url":"https://insights.sbomify.com/CVE-2025-35434/"}