{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8445 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8445 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8445 is a medium-severity vulnerability in Elastic X-Pack Security, published on 18 Aug 2017. 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-2017-8445 and fix it if it is affected.\n\nWhat it is: CVE-2017-8445 is a medium-severity vulnerability in Elastic X-Pack Security, published on 18 Aug 2017. 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-2017-8445 in the wild and no public exploit code.\n\nAffected product: Elastic X-Pack Security. 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-2017-8445/ (Markdown: https://insights.sbomify.com/CVE-2017-8445/index.md)","id":"CVE-2017-8445","markdown":"https://insights.sbomify.com/CVE-2017-8445/index.md","name":"CVE-2017-8445","record":{"aliases":["GHSA-fx8w-2fv7-5cq2"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elastic X-Pack Security","requires_auth":"low_privilege","summary":"A failure in TLS trust manager reloading allows any node with any certificate to join a cluster, bypassing security controls.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"x-pack","vendor":"elastic"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An error was found in the X-Pack Security TLS trust manager for versions 5.0.0 to 5.5.1. If reloading the trust material fails the trust manager will be replaced with an instance that trusts all certificates. This could allow any node using any certificate to join a cluster. The proper behavior in this instance is for the TLS trust manager to deny all certificates.","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":"Security feature bypass in Elastic X-Pack Security","id":"CVE-2017-8445","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Privilege Management in X-Pack","id":"CVE-2017-8446"},"packages":[],"prev":{"headline":"Weak cryptography in Elastic Cloud Enterprise","id":"CVE-2017-8444"},"products":["Elastic X-Pack Security"],"published":"2017-08-18","related":[{"cvss_score":9.8,"headline":"Auth bypass in X-Pack Security","id":"CVE-2018-3822","kev_date_added":null,"published":"2018-03-30"},{"cvss_score":8.8,"headline":"Privilege escalation in Elastic X-Pack Alerting","id":"CVE-2017-8448","kev_date_added":null,"published":"2017-09-28"},{"cvss_score":8.8,"headline":"Privilege escalation in X-Pack Security","id":"CVE-2017-8438","kev_date_added":null,"published":"2017-06-05"},{"cvss_score":7.5,"headline":"Missing authorization in Elastic X-Pack Security","id":"CVE-2017-8450","kev_date_added":null,"published":"2017-06-16"},{"cvss_score":6.5,"headline":"Privilege escalation in Elastic X-Pack Security","id":"CVE-2017-8447","kev_date_added":null,"published":"2017-09-28"},{"cvss_score":6.5,"headline":"Information disclosure in Elasticsearch X-Pack Security","id":"CVE-2017-8442","kev_date_added":null,"published":"2017-07-07"},{"cvss_score":5.9,"headline":"Information disclosure in Elastic X-Pack Security","id":"CVE-2017-8449","kev_date_added":null,"published":"2017-06-16"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Elastic"]},"summary":"A failure in TLS trust manager reloading allows any node with any certificate to join a cluster, bypassing security controls.","url":"https://insights.sbomify.com/CVE-2017-8445/"}