{"answers":{"affected":"2 open source packages ship an affected version, including engine.io-client. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-10536 in the wild and no public exploit code.","fix":"Upgrade engine.io-client to 1.6.9 or later.","what":"CVE-2016-10536 is a medium-severity vulnerability in HackerOne engine.io-client node module, published on 31 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-10536 and fix it if it is affected.\n\nWhat it is: CVE-2016-10536 is a medium-severity vulnerability in HackerOne engine.io-client node module, published on 31 May 2018. 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-2016-10536 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- engine.io-client (npm): affected all versions; fixed in 1.6.9\n- engine.io-client (npm): affected all versions; fixed in 1.6.9\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-2016-10536/ (Markdown: https://insights.sbomify.com/CVE-2016-10536/index.md)","id":"CVE-2016-10536","markdown":"https://insights.sbomify.com/CVE-2016-10536/index.md","name":"CVE-2016-10536","record":{"aliases":["GHSA-4r4m-hjwj-43p8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js client library","requires_auth":"none","summary":"Attackers can bypass TLS certificate validation in engine.io-client due to improper handling of null settings, enabling man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"engine.io-client","vendor":"socket"}],"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"},{"id":"CWE-300","name":"Channel Accessible by Non-Endpoint"}],"description":"engine.io-client is the client for engine.io, the implementation of a transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. The vulnerability is related to the way that node.js handles the `rejectUnauthorized` setting. If the value is something that evaluates to false, certificate verification will be disabled. This is problematic as engine.io-client 1.6.8 and earlier passes in an object for settings that includes the rejectUnauthorized property, whether it has been set or not. If the value has not been explicitly changed, it will be passed in as `null`, resulting in certificate verification being turned off.","ecosystems":["npm"],"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":"Insecure Defaults Allow MITM Over TLS in engine.io-client","id":"CVE-2016-10536","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2016"},"n_packages":2,"n_references":3,"next":{"headline":"Cross-Site Scripting in backbone","id":"CVE-2016-10537"},"packages":[{"ecosystem":"npm","fixed":["1.6.9"],"introduced":["0"],"last_affected":[],"package":"engine.io-client","purl":null,"source":"GHSA-4r4m-hjwj-43p8"},{"ecosystem":"npm","fixed":["1.6.9"],"introduced":["0"],"last_affected":[],"package":"engine.io-client","purl":"pkg:npm/engine.io-client","source":"GHSA-4r4m-hjwj-43p8"}],"prev":{"headline":"Timing Attack in csrf-lite","id":"CVE-2016-10535"},"products":["engine.io-client node module"],"published":"2018-05-31","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-17","vendors":["HackerOne"]},"summary":"Attackers can bypass TLS certificate validation in engine.io-client due to improper handling of null settings, enabling man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2016-10536/"}