{"answers":{"affected":"2 open source packages ship an affected version, including com.neovisionaries:nv-websocket-client. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000209 in the wild and no public exploit code.","fix":"Upgrade com.neovisionaries:nv-websocket-client to 2.1 or later.","what":"CVE-2017-1000209 is a medium-severity vulnerability in n/a, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1000209 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000209 is a medium-severity vulnerability in n/a, published on 17 Nov 2017. 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-2017-1000209 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.neovisionaries:nv-websocket-client (Maven): affected all versions; fixed in 2.1\n- com.neovisionaries:nv-websocket-client (Maven): affected all versions; fixed in 2.1\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-1000209/ (Markdown: https://insights.sbomify.com/CVE-2017-1000209/index.md)","id":"CVE-2017-1000209","markdown":"https://insights.sbomify.com/CVE-2017-1000209/index.md","name":"CVE-2017-1000209","record":{"aliases":["GHSA-4hxv-95rc-jqg7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Java WebSocket client","requires_auth":"none","summary":"Man-in-the-middle attackers can spoof SSL/TLS servers because the Java WebSocket client fails to verify hostname against certificate fields.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nv-websocket-client","vendor":"nv-websocket-client_project"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"The Java WebSocket client nv-websocket-client does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL/TLS servers via an arbitrary valid certificate.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"nv-websocket-client allows attackers to spoof SSL/TLS servers via an arbitrary valid certificate","id":"CVE-2017-1000209","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":2,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2017-1000210"},"packages":[{"ecosystem":"Maven","fixed":["2.1"],"introduced":["0"],"last_affected":[],"package":"com.neovisionaries:nv-websocket-client","purl":null,"source":"GHSA-4hxv-95rc-jqg7"},{"ecosystem":"Maven","fixed":["2.1"],"introduced":["0"],"last_affected":[],"package":"com.neovisionaries:nv-websocket-client","purl":"pkg:maven/com.neovisionaries/nv-websocket-client","source":"GHSA-4hxv-95rc-jqg7"}],"prev":{"headline":"Deserialization of Untrusted Data in swagger-parser","id":"CVE-2017-1000208"},"products":["n/a"],"published":"2017-11-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-09-16","vendors":["n/a"]},"summary":"Man-in-the-middle attackers can spoof SSL/TLS servers because the Java WebSocket client fails to verify hostname against certificate fields.","url":"https://insights.sbomify.com/CVE-2017-1000209/"}