{"answers":{"affected":"2 open source packages ship an affected version, including sails. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-10549 in the wild and no public exploit code.","fix":"Upgrade sails to 0.12.7 or later.","what":"CVE-2016-10549 is a medium-severity vulnerability in HackerOne sails node module, published on 31 May 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2016-10549 and fix it if it is affected.\n\nWhat it is: CVE-2016-10549 is a medium-severity vulnerability in HackerOne sails node module, published on 31 May 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2016-10549 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sails (npm): affected all versions; fixed in 0.12.7\n- sails (npm): affected all versions; fixed in 0.12.7\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-10549/ (Markdown: https://insights.sbomify.com/CVE-2016-10549/index.md)","id":"CVE-2016-10549","markdown":"https://insights.sbomify.com/CVE-2016-10549/index.md","name":"CVE-2016-10549","record":{"aliases":["GHSA-qmv4-jgp7-mf68"],"analysis":{"component_type":"library","fix_type":"configuration_change","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Sails.js web framework","requires_auth":"low_privilege","summary":"Attackers can bypass Same Origin Policy via reflected CORS headers in Sails.js when specific non-default configurations are enabled.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"sails","vendor":"sailsjs"}],"cvss":{"score":4.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"Sails is an MVC style framework for building realtime web applications. Version 0.12.7 and lower have an issue with the CORS configuration where the value of the origin header is reflected as the value for the Access-Control-Allow-Origin header. This would allow an attacker to make AJAX requests to vulnerable hosts through cross site scripting or a malicious HTML Document, effectively bypassing the Same Origin Policy. Note that this is only an issue when `allRoutes` is set to `true` and `origin` is set to `*` or left commented out in the sails CORS config file. The problem can be compounded when the cors `credentials` setting is not provided. At that point authenticated cross domain requests are possible.","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":"Sails before 0.12.7 vulnerable to Broken CORS","id":"CVE-2016-10549","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2016"},"n_packages":2,"n_references":3,"next":{"headline":"SQL Injection in sequelize","id":"CVE-2016-10550"},"packages":[{"ecosystem":"npm","fixed":["0.12.7"],"introduced":["0"],"last_affected":[],"package":"sails","purl":null,"source":"GHSA-qmv4-jgp7-mf68"},{"ecosystem":"npm","fixed":["0.12.7"],"introduced":["0"],"last_affected":[],"package":"sails","purl":"pkg:npm/sails","source":"GHSA-qmv4-jgp7-mf68"}],"prev":{"headline":"Arbitrary Code Injection in reduce-css-calc","id":"CVE-2016-10548"},"products":["sails node module"],"published":"2018-05-31","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":7.5,"headline":"Improper Input Validation in sails-hook-sockets","id":"CVE-2018-21036","kev_date_added":null,"published":"2020-07-21"}],"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 Same Origin Policy via reflected CORS headers in Sails.js when specific non-default configurations are enabled.","url":"https://insights.sbomify.com/CVE-2016-10549/"}