{"answers":{"affected":"2 open source packages ship an affected version, including sails-hook-sockets. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-21036 in the wild and no public exploit code.","fix":"Upgrade sails-hook-sockets to 1.5.5 or later.","what":"CVE-2018-21036 is a high-severity denial of service vulnerability in n/a, published on 21 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-21036 and fix it if it is affected.\n\nWhat it is: CVE-2018-21036 is a high-severity denial of service vulnerability in n/a, published on 21 Jul 2020. 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-2018-21036 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sails-hook-sockets (npm): affected all versions; fixed in 1.5.5\n- sails-hook-sockets (npm): affected all versions; fixed in 1.5.5\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-2018-21036/ (Markdown: https://insights.sbomify.com/CVE-2018-21036/index.md)","id":"CVE-2018-21036","markdown":"https://insights.sbomify.com/CVE-2018-21036/index.md","name":"CVE-2018-21036","record":{"aliases":["GHSA-f7f4-hqp2-7prc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Sails.js framework","requires_auth":"none","summary":"Attackers can cause a denial of service in Sails.js applications by sending a WebSocket request with an empty pathname due to missing error handling.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sails","vendor":"sailsjs"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Sails.js before v1.0.0-46 allows attackers to cause a denial of service with a single request because there is no error handler in sails-hook-sockets to handle an empty pathname in a WebSocket request.","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":"Improper Input Validation in sails-hook-sockets","id":"CVE-2018-21036","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2018"},"n_packages":2,"n_references":4,"next":{"headline":"Subrion CMS CSRF Vulnerability","id":"CVE-2018-21037"},"packages":[{"ecosystem":"npm","fixed":["1.5.5"],"introduced":["0"],"last_affected":[],"package":"sails-hook-sockets","purl":null,"source":"GHSA-f7f4-hqp2-7prc"},{"ecosystem":"npm","fixed":["1.5.5"],"introduced":["0"],"last_affected":[],"package":"sails-hook-sockets","purl":"pkg:npm/sails-hook-sockets","source":"GHSA-f7f4-hqp2-7prc"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-21035"},"products":["n/a"],"published":"2020-07-21","related":[{"cvss_score":9.8,"headline":"Prototype Pollution in Sails.js","id":"CVE-2021-44908","kev_date_added":null,"published":"2022-03-17"},{"cvss_score":7.5,"headline":"Sails DoS vulnerability for apps with sockets enabled","id":"CVE-2023-38504","kev_date_added":null,"published":"2023-07-27"},{"cvss_score":4.4,"headline":"Sails before 0.12.7 vulnerable to Broken CORS","id":"CVE-2016-10549","kev_date_added":null,"published":"2018-05-31"}],"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-08-05","vendors":["n/a"]},"summary":"Attackers can cause a denial of service in Sails.js applications by sending a WebSocket request with an empty pathname due to missing error handling.","url":"https://insights.sbomify.com/CVE-2018-21036/"}